From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25856 invoked by alias); 10 Jul 2018 17:58:19 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 25820 invoked by uid 48); 10 Jul 2018 17:58:15 -0000 From: "juergen.reuter at desy dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/86468] New: [9.0 regression] ICE verify_gimple failed Date: Tue, 10 Jul 2018 18:43:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: juergen.reuter at desy dot de X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00669.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86468 Bug ID: 86468 Summary: [9.0 regression] ICE verify_gimple failed Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: juergen.reuter at desy dot de Target Milestone: --- The following coarray code from c.l.f. 2016, Nov 16 leads to an ICE: $ gfortran -fcoarray=3Dsingle coarr1.f90 coarr1.f90:18:0: subroutine wrapped_point_add(self, to_add) Error: non-trivial conversion at assignment struct array02_integer(kind=3D4) struct array01_integer(kind=3D4) _36->point =3D point; coarr1.f90:18:0: internal compiler error: verify_gimple failed and here is the code: module classes implicit none private public :: wrapped_coarray type :: wrapped_point integer, allocatable :: point(:) contains procedure :: add =3D> wrapped_point_add end type wrapped_point type :: wrapped_coarray type(wrapped_point), allocatable :: caf(:)[:] end type wrapped_coarray contains subroutine wrapped_point_add(self, to_add) class(wrapped_point), intent(inout) :: self integer, intent(in) :: to_add integer, allocatable :: point(:) integer :: points_number if (allocated(self%point)) then points_number =3D size(self%point, dim=3D1) allocate(point(1:points_number+1)) point(1:points_number) =3D self%point point(points_number+1) =3D to_add call move_alloc(from=3Dpoint, to=3Dself%point) else allocate(self%point(1)) self%point(1) =3D to_add end if end subroutine wrapped_point_add end module classes program test use classes implicit none type(wrapped_coarray) :: foo allocate(foo%caf(99)[*]) call foo%caf(32)%add(this_image()) print*, foo%caf(32)%point end program test >>From gcc-bugs-return-609565-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 18:43:32 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 10424 invoked by alias); 10 Jul 2018 18:43:31 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 10386 invoked by uid 48); 10 Jul 2018 18:43:27 -0000 From: "jg at jguk dot org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/86469] New: Dwarf Error: Offset (1678049557) greater than or equal to .debug_str size (5846). Date: Tue, 10 Jul 2018 18:46:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jg at jguk dot org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00670.txt.bz2 Content-length: 3099 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86469 Bug ID: 86469 Summary: Dwarf Error: Offset (1678049557) greater than or equal to .debug_str size (5846). Product: gcc Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: jg at jguk dot org Target Milestone: --- Is this a known issue? I saw some other tickets but am not knowledgeable. O= r is it an LD issue? It's easy enough to reproduce, it is a function which doesn't match the protottype void get_err_whois(int wh_res, string & err_str); void get_err_whois(wh_res_e wh_res, string & err_str) { // implementation } I don't yet have a small test case. $ g++-8 --version g++-8 (Ubuntu 8-20180414-1ubuntu2) 8.0.1 20180414 (experimental) [trunk revision 259383] 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. $ make g++-8 -std=3Dc++11 -g -ggdb -pthread -O0 -Werror -Wextra -Wshadow -Wformat-nonliteral -Wall -Wnonnull -Wpedantic -fstack-protector-strong=20 -Wdiv-by-zero -Wsign-conversion -Wnull-dereference -flto -Wno-nonnull-compa= re -o proc main.cpp test_whois.cpp /usr/bin/x86_64-linux-gnu-ld: Dwarf Error: Offset (1678049557) greater than= or equal to .debug_str size (5846). /usr/bin/x86_64-linux-gnu-ld: Dwarf Error: Invalid abstract instance DIE re= f. /tmp/ccDxn2Yd.ltrans0.ltrans.o: In function `process_whois(std::__cxx11::basic_string, std::allocator > const&, bool, std::__cxx11::basic_string, std::allocator > const&, domain_s&)': :(.text+0xd554): undefined reference to `get_err_whois(int, std::__cxx11::basic_string, std::allocator >&)' :(.text+0xd75b): undefined reference to `get_err_whois(int, std::__cxx11::basic_string, std::allocator >&)' :(.text+0xdbca): undefined reference to `get_err_whois(int, std::__cxx11::basic_string, std::allocator >&)' /tmp/ccDxn2Yd.ltrans0.ltrans.o: In function `get_whois(std::__cxx11::basic_string, std::allocator > const&, bool, std::__cxx11::basic_string, std::allocator > const&, whoisinfo&, bool&, b= ool, bool, EWhois_t)': :(.text+0x20717): undefined reference to `get_err_whois(int, std::__cxx11::basic_string, std::allocator >&)' /tmp/ccDxn2Yd.ltrans0.ltrans.o: In function `test_whois(bool)': :(.text+0x6e827): undefined reference to `get_err_whois(int, std::__cxx11::basic_string, std::allocator >&)' collect2: error: ld returned 1 exit status makefile:3: recipe for target 'all' failed make: *** [all] Error 1 >>From gcc-bugs-return-609566-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 18:46:52 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 13791 invoked by alias); 10 Jul 2018 18:46:51 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 13673 invoked by uid 55); 10 Jul 2018 18:46:45 -0000 From: "sgk at troutmask dot apl.washington.edu" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/86450] Bootstrap failure due to -Wabi Date: Tue, 10 Jul 2018 18:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: blocker X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00671.txt.bz2 Content-length: 999 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86450 --- Comment #4 from Steve Kargl -= -- On Tue, Jul 10, 2018 at 09:55:15AM +0000, rguenth at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86450 >=20 > Richard Biener changed: >=20 > What |Removed |Added > -------------------------------------------------------------------------= --- > Keywords| |build > Component|bootstrap |libstdc++ >=20 > --- Comment #2 from Richard Biener --- > Can you check whether removing --enable-maintainer-mode fixes the build? = I've > not had this issue but I see those Wabi warnings as non-error. >=20 This is the likely problem that needs to be fixed. % find . -type f | xargs grep Wabi ... ./libstdc++-v3/acinclude.m4: WARN_FLAGS=3D'-Wall -Wextra -Wwrite-strings -Wcast-qual -Wabi' >>From gcc-bugs-return-609567-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 18:59:41 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 27837 invoked by alias); 10 Jul 2018 18:59:40 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 23120 invoked by uid 48); 10 Jul 2018 18:59:36 -0000 From: "juergen.reuter at desy dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/86470] New: ICE with OMP Date: Tue, 10 Jul 2018 19:04:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: juergen.reuter at desy dot de X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00672.txt.bz2 Content-length: 850 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86470 Bug ID: 86470 Summary: ICE with OMP Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: juergen.reuter at desy dot de Target Milestone: --- The code below leads to an ICE: $ gfortran -fopenmp omp2.f90=20 during GIMPLE pass: omplower omp2.f90:5:0: !$OMP PARALLEL private(val) internal compiler error: Segmentation fault: 11 libbacktrace could not find executable to open program select_type_openmp !$ use omp_lib implicit none class(*), allocatable :: val !$OMP PARALLEL private(val) allocate(integer::val) deallocate(val) !$OMP END PARALLEL end program select_type_openmp >>From gcc-bugs-return-609568-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 19:04:40 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 41093 invoked by alias); 10 Jul 2018 19:04:39 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 37013 invoked by uid 48); 10 Jul 2018 19:04:35 -0000 From: "ro at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/86461] [9 regression] test case gcc.c-torture/execute/builtins/strlen-3.c fails starting with r262522 Date: Tue, 10 Jul 2018 19:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: testsuite X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ro 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: cf_gcctarget cc cf_gcchost cf_gccbuild Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00673.txt.bz2 Content-length: 832 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86461 Rainer Orth changed: What |Removed |Added ---------------------------------------------------------------------------- Target|powerpc64*-*-* |powerpc64*-*-*, sparc*-*-*, | |aarch64-*-*, ia64-*-*, | |m68k-*-*, mips64el-*-* CC| |ro at gcc dot gnu.org Host|powerpc64*-*-* | Build|powerpc64*-*-* | --- Comment #2 from Rainer Orth --- Just for the record, I'm seeing the same failure on sparc (both 32 and 64-b= it), and there are gcc-testresults reports for a couple more targets. >>From gcc-bugs-return-609569-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 19:25:07 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 72856 invoked by alias); 10 Jul 2018 19:25:07 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 72661 invoked by uid 48); 10 Jul 2018 19:24:54 -0000 From: "paolo.carlini at oracle dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/59480] Missing error diagnostic: friend declaration specifying a default argument must be a definition Date: Tue, 10 Jul 2018 20:00:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: accepts-invalid, diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: paolo.carlini at oracle dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: paolo.carlini at oracle dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00674.txt.bz2 Content-length: 471 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D59480 Paolo Carlini changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |paolo.carlini at or= acle dot com --- Comment #7 from Paolo Carlini --- Mine. >>From gcc-bugs-return-609570-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 20:00:48 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 6164 invoked by alias); 10 Jul 2018 20:00:47 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 5615 invoked by uid 55); 10 Jul 2018 20:00:05 -0000 From: "sgk at troutmask dot apl.washington.edu" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/86450] Bootstrap failure due to -Wabi Date: Tue, 10 Jul 2018 20:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: blocker X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00675.txt.bz2 Content-length: 1628 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86450 --- Comment #5 from Steve Kargl -= -- On Tue, Jul 10, 2018 at 06:46:33PM +0000, sgk at troutmask dot apl.washington.edu wrote: >=20 > % find . -type f | xargs grep Wabi > ... > ./libstdc++-v3/acinclude.m4: WARN_FLAGS=3D'-Wall -Wextra -Wwrite-strings > -Wcast-qual -Wabi' >=20 This fixes the bootstrap failure Index: libstdc++-v3/acinclude.m4 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- libstdc++-v3/acinclude.m4 (revision 262541) +++ libstdc++-v3/acinclude.m4 (working copy) @@ -733,7 +733,7 @@ AC_DEFUN([GLIBCXX_EXPORT_FLAGS], [ # OPTIMIZE_CXXFLAGS =3D -O3 -fstrict-aliasing -fvtable-gc AC_SUBST(OPTIMIZE_CXXFLAGS) - WARN_FLAGS=3D'-Wall -Wextra -Wwrite-strings -Wcast-qual -Wabi' + WARN_FLAGS=3D'-Wall -Wextra -Wwrite-strings -Wcast-qual' AC_SUBST(WARN_FLAGS) ]) Index: libstdc++-v3/configure =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- libstdc++-v3/configure (revision 262541) +++ libstdc++-v3/configure (working copy) @@ -81846,7 +81846,7 @@ $as_echo "$gxx_include_dir" >&6; } # OPTIMIZE_CXXFLAGS =3D -O3 -fstrict-aliasing -fvtable-gc - WARN_FLAGS=3D'-Wall -Wextra -Wwrite-strings -Wcast-qual -Wabi' + WARN_FLAGS=3D'-Wall -Wextra -Wwrite-strings -Wcast-qual' >>From gcc-bugs-return-609571-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 20:13:59 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 34470 invoked by alias); 10 Jul 2018 20:13:59 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 33976 invoked by uid 48); 10 Jul 2018 20:13:53 -0000 From: "jg at jguk dot org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/86469] Dwarf Error: Offset (1678049557) greater than or equal to .debug_str size (5846). Date: Tue, 10 Jul 2018 20:22:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jg at jguk dot org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00676.txt.bz2 Content-length: 314 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86469 --- Comment #1 from Jonny Grant --- Perhaps G++ can check those dwarf offsets are within bounds when writing out the object files itself when saving obj files? Could output a useful warni= ng, when detected as an internal compiler error. >>From gcc-bugs-return-609572-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 20:22:15 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 80844 invoked by alias); 10 Jul 2018 20:22:15 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 80790 invoked by uid 55); 10 Jul 2018 20:22:10 -0000 From: "msebor at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/86461] [9 regression] test case gcc.c-torture/execute/builtins/strlen-3.c fails starting with r262522 Date: Tue, 10 Jul 2018 20:23:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: testsuite X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: msebor at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00677.txt.bz2 Content-length: 539 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86461 --- Comment #3 from Martin Sebor --- Author: msebor Date: Tue Jul 10 20:21:38 2018 New Revision: 262543 URL: https://gcc.gnu.org/viewcvs?rev=3D262543&root=3Dgcc&view=3Drev Log: PR testsuite/86461 - test case gcc.c-torture/execute/builtins/strlen-3.c fa= ils gcc/testsuite/ChangeLog: * gcc.c-torture/execute/builtins/strlen-3.c: Adjust. Modified: trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gcc.c-torture/execute/builtins/strlen-3.c >>From gcc-bugs-return-609573-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 20:23:19 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 83374 invoked by alias); 10 Jul 2018 20:23:18 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 83307 invoked by uid 48); 10 Jul 2018 20:23:14 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/86450] Bootstrap failure due to -Wabi Date: Tue, 10 Jul 2018 20:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: blocker X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00678.txt.bz2 Content-length: 934 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86450 --- Comment #6 from Jonathan Wakely --- (In reply to Steve Kargl from comment #3) > On Tue, Jul 10, 2018 at 09:55:15AM +0000, rguenth at gcc dot gnu.org wrot= e: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86450 > >=20 > > --- Comment #2 from Richard Biener --- > > Can you check whether removing --enable-maintainer-mode fixes the build= ? I've > > not had this issue but I see those Wabi warnings as non-error. > >=20 >=20 > Yes, removing --enable-maintainer-mode allows the bootstrap to=20 > complete. Problem is I need to use that option as I have change > a chnaged a Makefile.am, so need to regenerate the Makefile.in. I still don't understand this requirement. Using maintainer mode is not the only way to regenerate autoconf files, and has the downside of enabling -Werror. Can you try --disable-werror ? >>From gcc-bugs-return-609574-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 20:25:12 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 109021 invoked by alias); 10 Jul 2018 20:25:11 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 108876 invoked by uid 48); 10 Jul 2018 20:25:06 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/86450] Bootstrap failure due to -Wabi Date: Tue, 10 Jul 2018 20:26:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: blocker X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00679.txt.bz2 Content-length: 315 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86450 --- Comment #7 from Jonathan Wakely --- These warnings have been present for weeks - the idea that they're suddenly preventing anybody from working on gfortran is odd. Why can't you use autoc= onf=20 or autoreconf like everybody else? >>From gcc-bugs-return-609575-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 20:26:24 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 113993 invoked by alias); 10 Jul 2018 20:26:24 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 113761 invoked by uid 48); 10 Jul 2018 20:26:19 -0000 From: "msebor at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/86461] [9 regression] test case gcc.c-torture/execute/builtins/strlen-3.c fails starting with r262522 Date: Tue, 10 Jul 2018 20:30:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: testsuite X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: msebor at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00680.txt.bz2 Content-length: 792 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86461 Martin Sebor changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Martin Sebor --- There were a couple of problems with r262522: first, the dg-xxx directives = are ignored by the runtime torture tests, and second, whether or not all the st= rlen calls are eliminated depends on both optimization and the target. r262543 fixes both problems by reverting the previous change (and adding a comment explaining why it shouldn't be tightened up like that again). >>From gcc-bugs-return-609576-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 20:30:51 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 128555 invoked by alias); 10 Jul 2018 20:30:50 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 128245 invoked by uid 48); 10 Jul 2018 20:30:35 -0000 From: "mirq-gccboogs at rere dot qmqm.pl" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/66586] Template backtrace is truncated/absent after 'template argument deduction/substitution failed:' Date: Tue, 10 Jul 2018 20:32:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 5.1.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: mirq-gccboogs at rere dot qmqm.pl X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-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: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00681.txt.bz2 Content-length: 1366 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D66586 Micha=C5=82 Miros=C5=82aw changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mirq-gccboogs at rere dot = qmqm.pl --- Comment #3 from Micha=C5=82 Miros=C5=82aw --- Created attachment 44379 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D44379&action=3Dedit Testcase with enable_if_t Happens also in 6.3.0, 7.3.0, 8.1.0 (same messages generated for those versions). Slightly different testcase, with enable_if_t. $ g++ -c -std=3Dc++17 a.cc a.cc: In function =E2=80=98void bar()=E2=80=99: a.cc:22:7: error: no matching function for call to =E2=80=98foo(A&)=E2=80=99 foo(a); ^ a.cc:6:6: note: candidate: template void foo(S&) void foo(S&); ^~~ a.cc:6:6: note: template argument deduction/substitution failed: a.cc:9:6: note: candidate: template void foo(S&) void foo(S&); ^~~ a.cc:9:6: note: template argument deduction/substitution failed: a.cc:8:23: error: no type named =E2=80=98other=E2=80=99 in =E2=80=98struct = A=E2=80=99 template > ^~~~~~~~ >>From gcc-bugs-return-609577-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 20:32:04 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 2434 invoked by alias); 10 Jul 2018 20:32:03 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 2318 invoked by uid 48); 10 Jul 2018 20:31:59 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/82711] -Wignored-qualifiers could be moved into -Wextra Date: Tue, 10 Jul 2018 20:32:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00682.txt.bz2 Content-length: 182 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D82711 --- Comment #8 from Jonathan Wakely --- There was no change. r131499 was done more than a decade ago. >>From gcc-bugs-return-609578-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 20:32:16 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 3146 invoked by alias); 10 Jul 2018 20:32:16 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 3102 invoked by uid 48); 10 Jul 2018 20:32:12 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/82711] -Wignored-qualifiers could be moved into -Wextra Date: Tue, 10 Jul 2018 20:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WORKSFORME X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00683.txt.bz2 Content-length: 298 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D82711 Jonathan Wakely changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |WORKSFORME >>From gcc-bugs-return-609580-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 20:46:35 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 29095 invoked by alias); 10 Jul 2018 20:46:35 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 29047 invoked by uid 48); 10 Jul 2018 20:46:30 -0000 From: "tkoenig at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/86450] Bootstrap failure due to -Wabi Date: Tue, 10 Jul 2018 20:46:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: blocker X-Bugzilla-Who: tkoenig at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00685.txt.bz2 Content-length: 529 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86450 --- Comment #9 from Thomas Koenig --- (In reply to Jonathan Wakely from comment #7) > These warnings have been present for weeks - the idea that they're sudden= ly > preventing anybody from working on gfortran is odd. Why can't you use > autoconf or autoreconf like everybody else? It is odd that somebody who apparently does not know gfortran comes to such a judgement without knowing the details. Hint: Regenerating m4 files in libgfortran. >>From gcc-bugs-return-609579-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 20:35:54 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 8594 invoked by alias); 10 Jul 2018 20:35:54 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 8542 invoked by uid 48); 10 Jul 2018 20:35:49 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/86450] Bootstrap failure due to -Wabi Date: Tue, 10 Jul 2018 20:46:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: blocker X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00684.txt.bz2 Content-length: 997 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86450 --- Comment #8 from Jonathan Wakely --- (In reply to Steve Kargl from comment #5) > This fixes the bootstrap failure >=20 > Index: libstdc++-v3/acinclude.m4 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- libstdc++-v3/acinclude.m4 (revision 262541) > +++ libstdc++-v3/acinclude.m4 (working copy) > @@ -733,7 +733,7 @@ AC_DEFUN([GLIBCXX_EXPORT_FLAGS], [ > # OPTIMIZE_CXXFLAGS =3D -O3 -fstrict-aliasing -fvtable-gc > AC_SUBST(OPTIMIZE_CXXFLAGS) >=20=20 > - WARN_FLAGS=3D'-Wall -Wextra -Wwrite-strings -Wcast-qual -Wabi' > + WARN_FLAGS=3D'-Wall -Wextra -Wwrite-strings -Wcast-qual' > AC_SUBST(WARN_FLAGS) > ]) >=20=20 See https://gcc.gnu.org/ml/gcc-patches/2018-06/msg01923.html and https://gcc.gnu.org/ml/gcc-patches/2018-07/msg00059.html >>From gcc-bugs-return-609581-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 20:47:00 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 29808 invoked by alias); 10 Jul 2018 20:46:59 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 29777 invoked by uid 48); 10 Jul 2018 20:46:56 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/86464] Delegating constructor causes error if parameter has same name as class Date: Tue, 10 Jul 2018 20:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 8.1.0 X-Bugzilla-Keywords: rejects-valid X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on everconfirmed Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00686.txt.bz2 Content-length: 781 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86464 Jonathan Wakely changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |rejects-valid Status|UNCONFIRMED |NEW Last reconfirmed| |2018-07-10 Ever confirmed|0 |1 --- Comment #1 from Jonathan Wakely --- EDG accepts it but Clang also rejects it: del.cc:5:11: error: member initializer 'foo' does not name a non-static data member or base class : foo{ foo } ^~~~~~~~~~ But I think the code is valid according to [class.base.init] p2. >>From gcc-bugs-return-609582-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 20:49:44 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 78721 invoked by alias); 10 Jul 2018 20:49:44 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 69001 invoked by uid 55); 10 Jul 2018 20:49:39 -0000 From: "sgk at troutmask dot apl.washington.edu" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/86450] Bootstrap failure due to -Wabi Date: Tue, 10 Jul 2018 21:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: blocker X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00687.txt.bz2 Content-length: 524 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86450 --- Comment #10 from Steve Kargl = --- On Tue, Jul 10, 2018 at 08:35:48PM +0000, redi at gcc dot gnu.org wrote: >=20 > See https://gcc.gnu.org/ml/gcc-patches/2018-06/msg01923.html > and https://gcc.gnu.org/ml/gcc-patches/2018-07/msg00059.html >=20 Why do you think is a good idea for others to break the source? There is an obvious patch. I will commit my patch by the end of the day, or revert the patch causing the problem. >>From gcc-bugs-return-609583-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 21:20:26 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 20329 invoked by alias); 10 Jul 2018 21:20:26 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 20267 invoked by uid 48); 10 Jul 2018 21:20:21 -0000 From: "anlauf at gmx dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/86277] Presence of optional arguments not recognized for zero length arrays Date: Tue, 10 Jul 2018 21:37:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 8.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: anlauf at gmx dot de X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P4 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00688.txt.bz2 Content-length: 1055 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86277 Harald Anlauf changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anlauf at gmx dot de --- Comment #2 from Harald Anlauf --- Actually, the problem is not related to zero length arrays, but to the constructor [integer::]. I think this is related to several other PRs. program test implicit none integer :: m(0) integer, allocatable :: n(:) allocate (n(0)) call i call i(m) call i(n) call i([integer::]) ! expect "optional argument present: T" call i([1]) contains subroutine i(str) integer, dimension(:), optional, intent(in) :: str write(6,*) 'optional argument present:', present(str) end subroutine i end program produces: optional argument present: F optional argument present: T optional argument present: T optional argument present: F optional argument present: T >>From gcc-bugs-return-609584-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 21:37:46 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 52295 invoked by alias); 10 Jul 2018 21:37:45 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 52212 invoked by uid 48); 10 Jul 2018 21:37:41 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/86450] Bootstrap failure due to -Wabi Date: Tue, 10 Jul 2018 21:40:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: blocker X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00689.txt.bz2 Content-length: 710 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86450 --- Comment #11 from Jonathan Wakely --- (In reply to Thomas Koenig from comment #9) > (In reply to Jonathan Wakely from comment #7) > > These warnings have been present for weeks - the idea that they're sudd= enly > > preventing anybody from working on gfortran is odd. Why can't you use > > autoconf or autoreconf like everybody else? >=20 > It is odd that somebody who apparently does not know gfortran > comes to such a judgement without knowing the details. >=20 > Hint: Regenerating m4 files in libgfortran. Hint: maintainer mode is not magic, whatever it does can be done manually t= oo. And does --disable-werror help? >>From gcc-bugs-return-609585-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 21:40:23 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 62148 invoked by alias); 10 Jul 2018 21:40:23 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 61433 invoked by uid 48); 10 Jul 2018 21:40:17 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/86450] Bootstrap failure due to -Wabi Date: Tue, 10 Jul 2018 21:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: blocker X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00690.txt.bz2 Content-length: 756 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86450 --- Comment #12 from Jonathan Wakely --- (In reply to Steve Kargl from comment #10) > On Tue, Jul 10, 2018 at 08:35:48PM +0000, redi at gcc dot gnu.org wrote: > >=20 > > See https://gcc.gnu.org/ml/gcc-patches/2018-06/msg01923.html > > and https://gcc.gnu.org/ml/gcc-patches/2018-07/msg00059.html > >=20 >=20 > Why do you think is a good idea for others to > break the source? Where did I say that? > There is an obvious patch. > I will commit my patch by the end of the day, > or revert the patch causing the problem. OK. But gfortran being unable to cope with any warnings elsewhere in gcc without crying P1-blocker is the real problem, you really should address th= at. >>From gcc-bugs-return-609586-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 21:41:23 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 90390 invoked by alias); 10 Jul 2018 21:41:23 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 87340 invoked by uid 55); 10 Jul 2018 21:41:18 -0000 From: "sgk at troutmask dot apl.washington.edu" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/86450] Bootstrap failure due to -Wabi Date: Tue, 10 Jul 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: libstdc++ X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: blocker X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00691.txt.bz2 Content-length: 423 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86450 --- Comment #13 from Steve Kargl = --- On Tue, Jul 10, 2018 at 08:24:57PM +0000, redi at gcc dot gnu.org wrote: >=20 > --- Comment #7 from Jonathan Wakely --- > Why can't you use autoconf or autoreconf like everybody else? >=20 Why not fix the underlying issue? I will commit my patch later today. >>From gcc-bugs-return-609587-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 21:47:15 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 3048 invoked by alias); 10 Jul 2018 21:47:14 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 368 invoked by uid 48); 10 Jul 2018 21:47:10 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/86450] Bootstrap failure due to -Wabi Date: Tue, 10 Jul 2018 21:54:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: blocker X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00692.txt.bz2 Content-length: 630 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86450 --- Comment #14 from Jonathan Wakely --- Because we haven't decided what the fix is. Something like this seems better than dealing with each warning one by one every time this happens: --- a/libstdc++-v3/acinclude.m4 +++ b/libstdc++-v3/acinclude.m4 @@ -144,7 +144,8 @@ AC_DEFUN([GLIBCXX_CHECK_COMPILER_FEATURES], [ if test x"$USE_MAINTAINER_MODE" =3D xno; then WERROR=3D'' else - WERROR=3D'-Werror' + # -Werror breaks the build too often, don't enable it. + WERROR=3D'' fi # Check for -ffunction-sections -fdata-sections >>From gcc-bugs-return-609588-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 21:54:14 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 6289 invoked by alias); 10 Jul 2018 21:54:13 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 6197 invoked by uid 48); 10 Jul 2018 21:54:09 -0000 From: "tkoenig at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/86450] Bootstrap failure due to -Wabi Date: Tue, 10 Jul 2018 22:03:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: blocker X-Bugzilla-Who: tkoenig at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00693.txt.bz2 Content-length: 882 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86450 --- Comment #15 from Thomas Koenig --- (In reply to Jonathan Wakely from comment #11) > (In reply to Thomas Koenig from comment #9) > > (In reply to Jonathan Wakely from comment #7) > > > These warnings have been present for weeks - the idea that they're su= ddenly > > > preventing anybody from working on gfortran is odd. Why can't you use > > > autoconf or autoreconf like everybody else? > >=20 > > It is odd that somebody who apparently does not know gfortran > > comes to such a judgement without knowing the details. > >=20 > > Hint: Regenerating m4 files in libgfortran. >=20 > Hint: maintainer mode is not magic, whatever it does can be done manually > too. Sure - if something is broken, it is always better to point people to an unspecified workaround than to actually fix the problem. >>From gcc-bugs-return-609589-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 22:03:15 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 71130 invoked by alias); 10 Jul 2018 22:03:15 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 71056 invoked by uid 55); 10 Jul 2018 22:03:10 -0000 From: "sgk at troutmask dot apl.washington.edu" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/86450] Bootstrap failure due to -Wabi Date: Tue, 10 Jul 2018 22:11:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: blocker X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00694.txt.bz2 Content-length: 1102 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86450 --- Comment #16 from Steve Kargl = --- On Tue, Jul 10, 2018 at 09:40:16PM +0000, redi at gcc dot gnu.org wrote: >=20 > > There is an obvious patch. > > I will commit my patch by the end of the day, > > or revert the patch causing the problem. >=20 > OK. But gfortran being unable to cope with any warnings elsewhere in gcc > without crying P1-blocker is the real problem, you really should address = that. >=20 I cannot control other developers, who commit patches, that lack adequately testing. I am unsure how to address the issue other than raising a PR. Being unable to bootstrap, certainly seems to be a blocking problem. Breaking the tree (and it seems that this issues has been known for a couple of weeks) and turning a blind eye seems to be rather unfriendly to other cwcontributors. PS: The description of --enable-maintainer-mode does not state that -Werror is added to the options. Why have an option that "regenerate[s] the Autoconf and Automake output files" if it cannot not be used? >>From gcc-bugs-return-609590-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 22:11:59 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 124050 invoked by alias); 10 Jul 2018 22:11:59 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 123913 invoked by uid 48); 10 Jul 2018 22:11:54 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/86450] Bootstrap failure due to -Wabi Date: Tue, 10 Jul 2018 22:24:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: blocker X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00695.txt.bz2 Content-length: 1275 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86450 --- Comment #17 from Jonathan Wakely --- The problem is that gfortran development is dependent on a gcc-wide build m= ode which affects more than just gfortran. There's no good reason that libstdc++ should be a blocker for you (for the record, the -Wabi flag has been present for years, and the -Werror consequence of maintainer mode has been there for years too, what changed was not in libstdc++ but g++). If you had (for example) a --enable-gfortran-maintainer-mode option that triggered the m4 regeneration then you wouldn't need to alter the build opt= ions for the rest of gcc. Or a makefile target that regenerated the files, without needing to enable maintainer mode globally. Or some other solution that was under your control and specific to your subsystem, that didn't depend on other components that you don't need to de= pend on. That aside, I think not setting -Werror in libstdc++ for maintainer mode is better than simply removing warning options. But I'm on holiday and not goi= ng to commit anything myself, so do whatever you need to do. I'll put -Wabi=3D= N back later if we decide it should be there, with a suitable value of N so it doe= sn't give the current warning. >>From gcc-bugs-return-609591-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 22:24:57 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 11963 invoked by alias); 10 Jul 2018 22:24:55 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 11735 invoked by uid 48); 10 Jul 2018 22:24:26 -0000 From: "mark at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/86459] [9 Regression] ICE in output_macinfo_op, at dwarf2out.c:28095 since r260297 Date: Tue, 10 Jul 2018 22:28:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: debug X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: mark at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status everconfirmed Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00696.txt.bz2 Content-length: 1602 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86459 Mark Wielaard changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 --- Comment #2 from Mark Wielaard --- (In reply to Mark Wielaard from comment #1) > Sorry I missed that testcase starting to fail. I don't currently have it = in > my tree, so I assume it was added after this commit? It was. But now the testcase is compiled with -g3. > Which changed output_macinfo_op as follows: >=20 > @@ -28070,7 +28092,7 @@ output_macinfo_op (macinfo_entry *ref) > node =3D find_AT_string (ref->info); > gcc_assert (node > && (node->form =3D=3D DW_FORM_strp > - || node->form =3D=3D DW_FORM_GNU_str_index)); > + || node->form =3D=3D dwarf_form (DW_FORM_strx))); ^^^^^^^^^^ > dw2_asm_output_data (1, ref->code, > ref->code =3D=3D DW_MACRO_define_strp > ? "Define macro strp" >=20 > So I assume it is this assert that is triggering. >=20 > dwarf_form () was also introduced in that patch and is: >=20 > +/* And similarly for forms. */ > +static inline enum dwarf_form > +dwarf_FORM (enum dwarf_form form) ^^^^^^^^^^ Doh! So, it is a simply typo. s/dwarf_from/dwarf_FORM/ https://gcc.gnu.org/ml/gcc-patches/2018-07/msg00521.html >>From gcc-bugs-return-609592-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 22:28:48 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 89252 invoked by alias); 10 Jul 2018 22:28:48 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 89202 invoked by uid 48); 10 Jul 2018 22:28:43 -0000 From: "mattreecebentley at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/86471] New: GCC/libstdc++ outputs inferior code for std::fill and std::fill_n vs std::memset on c-style arrays Date: Tue, 10 Jul 2018 22:32:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 7.3.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mattreecebentley 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: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00697.txt.bz2 Content-length: 2886 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86471 Bug ID: 86471 Summary: GCC/libstdc++ outputs inferior code for std::fill and std::fill_n vs std::memset on c-style arrays Product: gcc Version: 7.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: mattreecebentley at gmail dot com Target Milestone: --- Test setup:=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Xubuntu 18, Core2Duo E8500 CPU, GCC 7.3 Results in release mode (-O2 -march=3Dnative): =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 2018-07-10 21:28:11 Running ./google_benchmark_test Run on (2 X 3800.15 MHz CPU s) CPU Caches: L1 Data 32K (x2) L1 Instruction 32K (x2) L2 Unified 6144K (x1) ----------------------------------------------------- Benchmark Time CPU Iterations ----------------------------------------------------- memory_filln 16488 ns 16477 ns 42460 memory_fill 16493 ns 16493 ns 42440 memory_memset 8414 ns 8408 ns 83022 Results in debug mode (-O0): =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D 2018-07-10 21:48:09 Running ./google_benchmark_test Run on (2 X 3800.15 MHz CPU s) CPU Caches: L1 Data 32K (x2) L1 Instruction 32K (x2) L2 Unified 6144K (x1) ----------------------------------------------------- Benchmark Time CPU Iterations ----------------------------------------------------- memory_filln 87209 ns 87139 ns 8029 memory_fill 94593 ns 94533 ns 7411 memory_memset 8441 ns 8434 ns 82833 Code: =3D=3D=3D=3D=3D=3D // Uses Google Benchmark. Rearrange the code any way you want, results stay similar: #include #include #include static void memory_memset(benchmark::State& state) { int ints[50000]; for (auto _ : state) { std::memset(ints, 0, sizeof(int) * 50000); } } static void memory_filln(benchmark::State& state) { int ints[50000]; for (auto _ : state) { std::fill_n(ints, 50000, 0); } } static void memory_fill(benchmark::State& state) { int ints[50000]; for (auto _ : state) { std::fill(std::begin(ints), std::end(ints), 0); } } // Register the function as a benchmark BENCHMARK(memory_filln); BENCHMARK(memory_fill); BENCHMARK(memory_memset); int main (int argc, char ** argv) { benchmark::Initialize (&argc, argv); benchmark::RunSpecifiedBenchmarks (); return 0; } >>From gcc-bugs-return-609593-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 22:32:58 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 103050 invoked by alias); 10 Jul 2018 22:32:58 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 103005 invoked by uid 48); 10 Jul 2018 22:32:54 -0000 From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/86471] GCC/libstdc++ outputs inferior code for std::fill and std::fill_n vs std::memset on c-style arrays Date: Tue, 10 Jul 2018 22:40:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 7.3.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00698.txt.bz2 Content-length: 234 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86471 --- Comment #1 from Andrew Pinski --- Does -O3 bring the performance back? -O3 enables loop distrubtion which sh= ould be able to detect these loops. >>From gcc-bugs-return-609594-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 22:40:35 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 13415 invoked by alias); 10 Jul 2018 22:40:35 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 13371 invoked by uid 48); 10 Jul 2018 22:40:30 -0000 From: "mattreecebentley at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/86471] GCC/libstdc++ outputs inferior code for std::fill and std::fill_n vs std::memset on c-style arrays Date: Tue, 10 Jul 2018 22:42:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 7.3.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mattreecebentley 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: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00699.txt.bz2 Content-length: 448 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86471 --- Comment #2 from Matt Bentley --- (In reply to Andrew Pinski from comment #1) > Does -O3 bring the performance back? -O3 enables loop distrubtion which > should be able to detect these loops. Just tested - yes. However this is a fairly trivial testcase and not all projects compile with= O3 (most don't). Clang by comparison optimizes this out at -O2. >>From gcc-bugs-return-609595-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 22:42:51 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 19925 invoked by alias); 10 Jul 2018 22:42:51 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 17577 invoked by uid 48); 10 Jul 2018 22:42:47 -0000 From: "mattreecebentley at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/86471] GCC/libstdc++ outputs inferior code for std::fill and std::fill_n vs std::memset on c-style arrays Date: Tue, 10 Jul 2018 22:45:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 7.3.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mattreecebentley 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: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00700.txt.bz2 Content-length: 1864 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86471 --- Comment #3 from Matt Bentley --- I thought I should note that there is also a missing optimization opportuni= ty in the code. Clang optimizes the code I've listed to remove the benchmark l= oops entirely since it detects that the arrays aren't actually being used for anything.=20 In order to get clang to benchmark it properly, I had to add a loop which a= dds the array contents to a total post-benchmark, as follows: #include #include #include double total =3D 0; static void memory_memset(benchmark::State& state) { int ints[50000]; for (auto _ : state) { std::memset(ints, 0, sizeof(int) * 50000); } for (int counter =3D 0; counter !=3D 50000; ++counter) { total +=3D ints[counter]; } } static void memory_filln(benchmark::State& state) { int ints[50000]; for (auto _ : state) { std::fill_n(ints, 50000, 0); } for (int counter =3D 0; counter !=3D 50000; ++counter) { total +=3D ints[counter]; } } static void memory_fill(benchmark::State& state) { int ints[50000]; for (auto _ : state) { std::fill(std::begin(ints), std::end(ints), 0); } for (int counter =3D 0; counter !=3D 50000; ++counter) { total +=3D ints[counter]; } } // Register the function as a benchmark BENCHMARK(memory_filln); BENCHMARK(memory_fill); BENCHMARK(memory_memset); int main (int argc, char ** argv) { benchmark::Initialize (&argc, argv); benchmark::RunSpecifiedBenchmarks (); printf("Total =3D %f\n", total); getchar(); return 0; } >>From gcc-bugs-return-609596-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 22:45:27 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 73861 invoked by alias); 10 Jul 2018 22:45:14 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 73632 invoked by uid 55); 10 Jul 2018 22:45:02 -0000 From: "mark at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/86459] [9 Regression] ICE in output_macinfo_op, at dwarf2out.c:28095 since r260297 Date: Tue, 10 Jul 2018 22: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: 9.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: mark at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00701.txt.bz2 Content-length: 830 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86459 --- Comment #3 from Mark Wielaard --- Author: mark Date: Tue Jul 10 22:44:30 2018 New Revision: 262545 URL: https://gcc.gnu.org/viewcvs?rev=3D262545&root=3Dgcc&view=3Drev Log: PR debug/86459 - Fix -gsplit-dwarf -g3 gcc_assert There was a typo in the output_macinfo_op gcc_assert. The function is called dwarf_FORM, not dwarf_form. Add the provided testcase from the bug to test -gsplit-dwarf -g3. gcc/ChangeLog: PR debug/86459 * dwarf2out.c (output_macinfo_op): Fix dwarf_FORM typo in gcc_asser= t. gcc/testsuite/ChangeLog: PR debug/86459 * gcc.dg/pr86459.c: New test. Added: trunk/gcc/testsuite/gcc.dg/pr86459.c Modified: trunk/gcc/ChangeLog trunk/gcc/dwarf2out.c trunk/gcc/testsuite/ChangeLog >>From gcc-bugs-return-609597-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 22:47:48 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 77656 invoked by alias); 10 Jul 2018 22:47:48 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 77597 invoked by uid 48); 10 Jul 2018 22:47:44 -0000 From: "mark at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/86459] [9 Regression] ICE in output_macinfo_op, at dwarf2out.c:28095 since r260297 Date: Tue, 10 Jul 2018 22:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: debug X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: mark at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00702.txt.bz2 Content-length: 428 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86459 Mark Wielaard changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Mark Wielaard --- commit pushed >>From gcc-bugs-return-609598-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 22:49:47 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 79597 invoked by alias); 10 Jul 2018 22:49:46 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 79523 invoked by uid 55); 10 Jul 2018 22:49:42 -0000 From: "sgk at troutmask dot apl.washington.edu" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/86450] Bootstrap failure due to -Wabi Date: Tue, 10 Jul 2018 23:18:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: blocker X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00703.txt.bz2 Content-length: 2352 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86450 --- Comment #18 from Steve Kargl = --- On Tue, Jul 10, 2018 at 10:11:54PM +0000, redi at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86450 >=20 > --- Comment #17 from Jonathan Wakely --- > The problem is that gfortran development is dependent > on a gcc-wide build mode which affects more than just > gfortran. There's no good reason that libstdc++ should > be a blocker for you (for the record, the -Wabi flag > has been present for years, and the -Werror consequence > of maintainer mode has been there for years too, what > changed was not in libstdc++ but g++). https://gcc.gnu.org/install/configure.html --enable-maintainer-mode The build rules that regenerate the Autoconf and Automake output files as well as the GCC master message catalog gcc.pot are normally disabled. This is because it can only be rebuilt if the complete source tree is present. If you have changed the sources and want to rebuild the catalog, configuring with --enable-maintainer-mode will enable this. Note that you need a recent version of the gettext tools to do so. It seems the gfortran contributors use --enable-maintainer-mode as documented. It does not state that -Werror magically appears. It does not say that this option should only be used by an annointed individual. The -Wabi option may have been around for years, but it only recently became a noise emitting useless option. 2018-06-13 Jason Merrill * c-opts.c (c_common_post_options): Warn about useless -Wabi. (c_common_handle_option) [OPT_Wabi_]: Remove flag_abi_compat_version handling. I also did not state that libstdc++ was a blocker. The blocker is that bootstrap is broken for me. I wrote BOOTSTRAP. Yes, it was a change in g++ that is the root cause. Unfortunately, the root cause is triggered in libstdc++, because -Wabi has changed, and for some reason libstdc++ developers seem too opposed to fixing the issue! What I find distressing is that I wasted a day finding the problem and developing a patch that was proposed 2 weeks ago. Your review was "No, I don't think we want to simply remove it [-Wabi]." The three follow-up were of the same quality with no actual resolution. >>From gcc-bugs-return-609600-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 00:25:16 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 5203 invoked by alias); 11 Jul 2018 00:25:15 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 5160 invoked by uid 48); 11 Jul 2018 00:25:10 -0000 From: "zhonghao at pku dot org.cn" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/86473] New: a problem in member lookup? Date: Wed, 11 Jul 2018 00:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 8.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: zhonghao at pku dot org.cn X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-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: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00705.txt.bz2 Content-length: 1549 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86473 Bug ID: 86473 Summary: a problem in member lookup? Product: gcc Version: 8.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: zhonghao at pku dot org.cn Target Milestone: --- The code is as follows: namespace PR5820 { struct Base {}; struct D1 : public Base {}; struct D2 : public Base {}; struct Derived : public D1, public D2 { void Inner() { } }; } template struct BaseT { int Member; }; template struct Derived1T : BaseT { }; template struct Derived2T : BaseT { }; template struct DerivedT : public Derived1T, public Derived2T { void Inner(); }; template void Test(DerivedT d) { d.template Derived2T::Member =3D 17; } template void Test(DerivedT); ------------------------------------- g++ rejects the code: code0.cpp: In function 'void Test(DerivedT)': code0.cpp:27:25: error: expected ';' before '::' token d.template Derived2T::Member =3D 17; ^~ ; code0.cpp: In instantiation of 'void Test(DerivedT) [with T =3D int]': code0.cpp:30:33: required from here code0.cpp:27:13: error: 'Derived2T' is not a member template function d.template Derived2T::Member =3D 17; ~~~~~~~~~~~^~~~~~~~~~~~ This code looks legal for me. Clang++ accepts the code. >>From gcc-bugs-return-609599-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 23:18:42 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 113257 invoked by alias); 10 Jul 2018 23:18:15 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 112703 invoked by uid 48); 10 Jul 2018 23:17:29 -0000 From: "jfeng33 at hotmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/86472] New: allocatable array, bound-procedure, submodule Date: Wed, 11 Jul 2018 00:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 8.1.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jfeng33 at hotmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00704.txt.bz2 Content-length: 1336 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86472 Bug ID: 86472 Summary: allocatable array, bound-procedure, submodule Product: gcc Version: 8.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: jfeng33 at hotmail dot com Target Milestone: --- Module M1 implicit none type :: mytype contains procedure :: myfunc1 end type interface module subroutine myfunc1(self, a) class(mytype), intent(in) :: self real, intent(in) :: a(:) real, allocatable :: t(:) end subroutine myfunc1 end interface End Module M1 ------------------------------------------ submodule(M1) M2 contains module procedure myfunc1 ! real, allocatable :: t(:) allocate(t, source=3Da) x=3D10.0 print *,t, a, x end procedure myfunc1 end submodule M2 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D submodule M2 showed compilation error (Error: Allocate-object is neither a data pointer nor an allocatable variable) without re-declare variable t. Al= so un-declared variable x gives no error. >>From gcc-bugs-return-609601-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 00:25:56 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 6378 invoked by alias); 11 Jul 2018 00:25:55 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 6168 invoked by uid 48); 11 Jul 2018 00:25:50 -0000 From: "zhonghao at pku dot org.cn" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/86474] New: a problem in member lookup? Date: Wed, 11 Jul 2018 00:35: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: zhonghao at pku dot org.cn X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-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: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00706.txt.bz2 Content-length: 1549 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86474 Bug ID: 86474 Summary: a problem in member lookup? Product: gcc Version: 8.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: zhonghao at pku dot org.cn Target Milestone: --- The code is as follows: namespace PR5820 { struct Base {}; struct D1 : public Base {}; struct D2 : public Base {}; struct Derived : public D1, public D2 { void Inner() { } }; } template struct BaseT { int Member; }; template struct Derived1T : BaseT { }; template struct Derived2T : BaseT { }; template struct DerivedT : public Derived1T, public Derived2T { void Inner(); }; template void Test(DerivedT d) { d.template Derived2T::Member =3D 17; } template void Test(DerivedT); ------------------------------------- g++ rejects the code: code0.cpp: In function 'void Test(DerivedT)': code0.cpp:27:25: error: expected ';' before '::' token d.template Derived2T::Member =3D 17; ^~ ; code0.cpp: In instantiation of 'void Test(DerivedT) [with T =3D int]': code0.cpp:30:33: required from here code0.cpp:27:13: error: 'Derived2T' is not a member template function d.template Derived2T::Member =3D 17; ~~~~~~~~~~~^~~~~~~~~~~~ This code looks legal for me. Clang++ accepts the code. >>From gcc-bugs-return-609602-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 00:35:02 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 63412 invoked by alias); 11 Jul 2018 00:35:02 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 63338 invoked by uid 48); 11 Jul 2018 00:34:57 -0000 From: "zhonghao at pku dot org.cn" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/86475] New: CWG 1550 Date: Wed, 11 Jul 2018 00:40: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: zhonghao at pku dot org.cn X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-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: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00707.txt.bz2 Content-length: 1225 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86475 Bug ID: 86475 Summary: CWG 1550 Product: gcc Version: 8.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: zhonghao at pku dot org.cn Target Milestone: --- I looked around to see if a bug was already filed on this and couldn't find one. CWG 1550, passed in Bristol, changes the value category of the result of a conditional operator when one operand is an lvalue and the other is a throw-expression: * The second or the third operand (but not both) is a (possibly parenthesiz= ed) throw-expression (15.1); the result is of the type and value category of the other. Here is a test, that should compile in C++: struct X { int i_; bool b_; int& test() {return b_ ? i_ : throw 1;} }; Current behavior is: error: cannot bind non-const lvalue reference of type 'int&' to an rvalue = of type 'int' int& test() {return b_ ? i_ : throw 1;} ~~~^~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~ 1 error generated. I tried clang++. It accepts the code. >>From gcc-bugs-return-609603-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 00:40:25 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 19134 invoked by alias); 11 Jul 2018 00:40:24 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 19090 invoked by uid 48); 11 Jul 2018 00:40:20 -0000 From: "zhonghao at pku dot org.cn" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/86476] New: Members declared later in a class appear to be unavailable Date: Wed, 11 Jul 2018 00:52:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 8.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: zhonghao at pku dot org.cn X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-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: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00708.txt.bz2 Content-length: 842 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86476 Bug ID: 86476 Summary: Members declared later in a class appear to be unavailable Product: gcc Version: 8.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: zhonghao at pku dot org.cn Target Milestone: --- The code is as follows: template struct A { void f() noexcept(noexcept(m.f())) { m.f(); } T m; }; struct B { void f(); }; int main() { A a; a.f(); } g++ produces: error: 'm' was not declared in this scope void f() noexcept(noexcept(m.f())) { What gives? Surely A is complete in this context and we can see m? I tried clang++. It accepts the code. >>From gcc-bugs-return-609604-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 00:52:56 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 50640 invoked by alias); 11 Jul 2018 00:52:55 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 50556 invoked by uid 48); 11 Jul 2018 00:52:52 -0000 From: "zhonghao at pku dot org.cn" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/86477] New: failure binding reference to vector element Date: Wed, 11 Jul 2018 01:10:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 8.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: zhonghao at pku dot org.cn X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-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: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00709.txt.bz2 Content-length: 717 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86477 Bug ID: 86477 Summary: failure binding reference to vector element Product: gcc Version: 8.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: zhonghao at pku dot org.cn Target Milestone: --- The code is as follows: typedef __attribute__((ext_vector_type(4))) int vi4; const int &r =3D vi4(1).x; g++ rejects it: error: request for member 'x' in '1', which is of non-class type 'vi4' {aka 'int'} const int &r =3D vi4(1).x; clang++ accepts the code. It looks like well-formed, right? >>From gcc-bugs-return-609605-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 01:10:32 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 17221 invoked by alias); 11 Jul 2018 01:10:32 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 17168 invoked by uid 48); 11 Jul 2018 01:10:27 -0000 From: "zhonghao at pku dot org.cn" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/86478] New: Crashed on legal code Date: Wed, 11 Jul 2018 01: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: zhonghao at pku dot org.cn X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-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: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00710.txt.bz2 Content-length: 2913 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86478 Bug ID: 86478 Summary: Crashed on legal code Product: gcc Version: 8.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: zhonghao at pku dot org.cn Target Milestone: --- The code is as follows: template struct X {}; template void foo(X... a); void test() { foo(X(), X()); } g++ crashes when compiling the code: code0.cpp: In substitution of 'template void foo(X..= .) [with T =3D ]': code0.cpp:10:53: required from here code0.cpp:10:53: internal compiler error: tree check: expected class 'expression', have 'type' (integer_type) in tree_operand_check, at tree.h:3= 633 foo(X(), X()); ^ 0x79b1a2 tree_class_check_failed(tree_node const*, tree_code_class, char const*, int, char const*) ../../code/gcc/tree.c:9377 0x65b01a expr_check(tree_node*, char const*, int, char const*) ../../code/gcc/tree.h:3304 0x65b01a tree_operand_check(tree_node*, int, char const*, int, char const*) ../../code/gcc/tree.h:3633 0x65b01a unify_pack_expansion ../../code/gcc/cp/pt.c:20777 0x990032 unify ../../code/gcc/cp/pt.c:21565 0x98edf3 unify ../../code/gcc/cp/pt.c:21762 0x98fe10 unify ../../code/gcc/cp/pt.c:21559 0x98e8a2 try_class_unification ../../code/gcc/cp/pt.c:20559 0x990925 unify ../../code/gcc/cp/pt.c:21596 0x9958a3 unify_one_argument ../../code/gcc/cp/pt.c:19793 0x996520 unify_pack_expansion ../../code/gcc/cp/pt.c:20808 0x997ab6 type_unification_real ../../code/gcc/cp/pt.c:19933 0x998ab5 fn_type_unification(tree_node*, tree_node*, tree_node*, tree_node* const*, unsigned int, tree_node*, unification_kind_t, int, bool, bool) ../../code/gcc/cp/pt.c:19298 0x839f0f add_template_candidate_real ../../code/gcc/cp/call.c:3179 0x83a920 add_template_candidate ../../code/gcc/cp/call.c:3258 0x83a920 add_candidates ../../code/gcc/cp/call.c:5520 0x83ad31 add_candidates ../../code/gcc/cp/call.c:4192 0x83ad31 perform_overload_resolution ../../code/gcc/cp/call.c:4200 0x83cda2 build_new_function_call(tree_node*, vec**, int) ../../code/gcc/cp/call.c:4273 0x9bb475 finish_call_expr(tree_node*, vec**, b= ool, bool, int) ../../code/gcc/cp/semantics.c:2534 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See for instructions. Clang++ accepts the above code. >>From gcc-bugs-return-609606-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 01:56:37 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 79760 invoked by alias); 11 Jul 2018 01:56:36 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 78777 invoked by uid 48); 11 Jul 2018 01:56:31 -0000 From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/86477] failure binding reference to vector element Date: Wed, 11 Jul 2018 05:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 8.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00711.txt.bz2 Content-length: 516 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86477 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Andrew Pinski --- There are no fields for vectors, only array accesses. Looks like clang is doing OpenCL like. >>From gcc-bugs-return-609607-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 05:35:38 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 81093 invoked by alias); 11 Jul 2018 05:35:38 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 81046 invoked by uid 48); 11 Jul 2018 05:35:34 -0000 From: "glisse at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/86477] failure binding reference to vector element Date: Wed, 11 Jul 2018 05:53:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 8.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: glisse at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00712.txt.bz2 Content-length: 336 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86477 --- Comment #2 from Marc Glisse --- We don't have attribute ext_vector_type (we have vector_size). Gcc warns ab= out it. We don't allow constructing a vector from a scalar (broadcasting). What Andrew says. If I fix everything, binding a reference works. >>From gcc-bugs-return-609608-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 05:53:47 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 126649 invoked by alias); 11 Jul 2018 05:53:47 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 126592 invoked by uid 48); 11 Jul 2018 05:53:42 -0000 From: "glisse at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/86471] GCC/libstdc++ outputs inferior code for std::fill and std::fill_n vs std::memset on c-style arrays Date: Wed, 11 Jul 2018 07:00:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 7.3.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: 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: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00713.txt.bz2 Content-length: 633 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86471 --- Comment #4 from Marc Glisse --- There have been questions before about enabling (parts of) ldist at -O2. (In reply to Matt Bentley from comment #3) > I thought I should note that there is also a missing optimization > opportunity in the code. Clang optimizes the code I've listed to remove t= he > benchmark loops entirely since it detects that the arrays aren't actually > being used for anything.=20 Indeed, I am surprised gcc didn't optimize out all those useless writes (in= ts is local and doesn't escape). Seems worth investigating a bit. >>From gcc-bugs-return-609610-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 07:09:28 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 31721 invoked by alias); 11 Jul 2018 07:09:27 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 25425 invoked by uid 48); 11 Jul 2018 07:09:22 -0000 From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/86457] [8 Regression] ICE in add_dwarf_attr, at dwarf2out.c:4405 since r251448 Date: Wed, 11 Jul 2018 07:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: debug X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.2 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: priority cf_known_to_work short_desc cf_known_to_fail Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00715.txt.bz2 Content-length: 754 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86457 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 |P2 Known to work| |9.0 Summary|[8/9 Regression] ICE in |[8 Regression] ICE in |add_dwarf_attr, at |add_dwarf_attr, at |dwarf2out.c:4405 since |dwarf2out.c:4405 since |r251448 |r251448 Known to fail|9.0 | --- Comment #2 from Richard Biener --- Fixed on trunk sofar. >>From gcc-bugs-return-609609-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 07:00:50 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 40650 invoked by alias); 11 Jul 2018 07:00:48 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 39071 invoked by uid 48); 11 Jul 2018 07:00:14 -0000 From: "asolokha at gmx dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/86479] New: [9 Regression] [graphite] ICE in gimplify_modify_expr, at gimplify.c:5756 Date: Wed, 11 Jul 2018 07:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: ice-on-invalid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: asolokha at gmx dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00714.txt.bz2 Content-length: 5026 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86479 Bug ID: 86479 Summary: [9 Regression] [graphite] ICE in gimplify_modify_expr, at gimplify.c:5756 Product: gcc Version: 9.0 Status: UNCONFIRMED Keywords: ice-on-invalid-code Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: asolokha at gmx dot com Target Milestone: --- gcc-9.0.0-alpha20180708 snapshot (r262505) ICEs when compiling the following snippet w/ -O2 (-O3, -Ofast) -floop-nest-optimize -fnon-call-exceptions -fno-guess-branch-probability -fno-tree-loop-im: long int uf; void m7 (long int *aw, long int ws) { long int *e5 =3D &ws; if (ws < 1) { int cq =3D 0; while (cq < 1) { int *ng; int *ud; *e5 *=3D uf < 0; for (*ng =3D 0; *ng < 2; ++*ng) { } ws /=3D cq; *aw *=3D ws; for (*ud =3D 0; *ud < 2; ++*ud) { } } } if (ws < 2) e5 =3D &uf; *e5 =3D 0; } % gcc-9.0.0-alpha20180708 -O2 -floop-nest-optimize -fnon-call-exceptions -fno-guess-branch-probability -fno-tree-loop-im -c ks550ciw.c during GIMPLE pass: graphite In function 'm7': cc1: internal compiler error: in gimplify_modify_expr, at gimplify.c:5756 0x60ff28 gimplify_modify_expr =20=20=20=20=20=20=20 /var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180708/work/gcc-9-20180708/gcc/= gimplify.c:5755 0xa311ba gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*= ), int) =20=20=20=20=20=20=20 /var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180708/work/gcc-9-20180708/gcc/= gimplify.c:11434 0xa33666 gimplify_stmt(tree_node**, gimple**) =20=20=20=20=20=20=20 /var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180708/work/gcc-9-20180708/gcc/= gimplify.c:6618 0xa3871e gimplify_cond_expr =20=20=20=20=20=20=20 /var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180708/work/gcc-9-20180708/gcc/= gimplify.c:4087 0xa31140 gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*= ), int) =20=20=20=20=20=20=20 /var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180708/work/gcc-9-20180708/gcc/= gimplify.c:11391 0xa33666 gimplify_stmt(tree_node**, gimple**) =20=20=20=20=20=20=20 /var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180708/work/gcc-9-20180708/gcc/= gimplify.c:6618 0xa38115 gimplify_cond_expr =20=20=20=20=20=20=20 /var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180708/work/gcc-9-20180708/gcc/= gimplify.c:3984 0xa31140 gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*= ), int) =20=20=20=20=20=20=20 /var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180708/work/gcc-9-20180708/gcc/= gimplify.c:11391 0xa2f542 gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*= ), int) =20=20=20=20=20=20=20 /var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180708/work/gcc-9-20180708/gcc/= gimplify.c:12157 0xa40b2c force_gimple_operand_1(tree_node*, gimple**, bool (*)(tree_node*), tree_node*) =20=20=20=20=20=20=20 /var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180708/work/gcc-9-20180708/gcc/= gimplify-me.c:78 0x143e9e1 translate_isl_ast_to_gimple::graphite_copy_stmts_from_block(basic_block_def= *, basic_block_def*, vec) =20=20=20=20=20=20=20 /var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180708/work/gcc-9-20180708/gcc/= graphite-isl-ast-to-gimple.c:1221 0x143feda translate_isl_ast_to_gimple::copy_bb_and_scalar_dependences(basic_block_def= *, edge_def*, vec) =20=20=20=20=20=20=20 /var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180708/work/gcc-9-20180708/gcc/= graphite-isl-ast-to-gimple.c:1270 0x1440631 translate_isl_ast_to_gimple::translate_isl_ast_node_user(isl_ast_node*, edge_def*, std::map, std::allocator > >&) =20=20=20=20=20=20=20 /var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180708/work/gcc-9-20180708/gcc/= graphite-isl-ast-to-gimple.c:830 0x1440d25 translate_isl_ast_to_gimple::translate_isl_ast_node_block(loop*, isl_ast_node*, edge_def*, std::map, std::allocator > >&) =20=20=20=20=20=20=20 /var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180708/work/gcc-9-20180708/gcc/= graphite-isl-ast-to-gimple.c:859 0x1441107 graphite_regenerate_ast_isl(scop*) =20=20=20=20=20=20=20 /var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180708/work/gcc-9-20180708/gcc/= graphite-isl-ast-to-gimple.c:1505 0x143d3d4 graphite_transform_loops() =20=20=20=20=20=20=20 /var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180708/work/gcc-9-20180708/gcc/= graphite.c:413 0x143d7d0 graphite_transforms =20=20=20=20=20=20=20 /var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180708/work/gcc-9-20180708/gcc/= graphite.c:475 0x143d7d0 execute =20=20=20=20=20=20=20 /var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180708/work/gcc-9-20180708/gcc/= graphite.c:552 >>From gcc-bugs-return-609611-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 07:09:33 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 33051 invoked by alias); 11 Jul 2018 07:09:33 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 30071 invoked by uid 55); 11 Jul 2018 07:09:26 -0000 From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/86457] [8 Regression] ICE in add_dwarf_attr, at dwarf2out.c:4405 since r251448 Date: Wed, 11 Jul 2018 07:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: debug X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.2 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00716.txt.bz2 Content-length: 636 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86457 --- Comment #3 from Richard Biener --- Author: rguenth Date: Wed Jul 11 07:08:54 2018 New Revision: 262551 URL: https://gcc.gnu.org/viewcvs?rev=3D262551&root=3Dgcc&view=3Drev Log: 2018-07-11 Richard Biener PR debug/86457 * dwarf2out.c (init_sections_and_labels): Use output_asm_line_debug_info consistently. (dwarf2out_early_finish): Likewise. (dwarf2out_finish): Remove DW_AT_stmt_list from early generated type units. Modified: trunk/gcc/ChangeLog trunk/gcc/dwarf2out.c >>From gcc-bugs-return-609612-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 07:20:17 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 51783 invoked by alias); 11 Jul 2018 07:20:17 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 51756 invoked by uid 48); 11 Jul 2018 07:20:12 -0000 From: "gufideg at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/86480] New: [8 Regression] error: parameter packs not expanded with '...' in a recursive variadic lambda Date: Wed, 11 Jul 2018 08:02:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 8.1.1 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: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00717.txt.bz2 Content-length: 4121 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86480 Bug ID: 86480 Summary: [8 Regression] error: parameter packs not expanded with '...' in a recursive variadic lambda Product: gcc Version: 8.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: gufideg at gmail dot com Target Milestone: --- The following code compiler with Clang and GCC 7.3: #include #include #include template>> struct tuple_sequence_helper; template struct tuple_sequence_helper> { using type =3D std::tuple...>; }; template constexpr auto apply_sequence(F function) -> decltype(auto) { return std::apply(function, typename tuple_sequence_helper>::type{}); } template struct drop_last_helper; template struct drop_last_helper> { using type =3D std::tuple...>; }; template struct drop_last; template struct drop_last> : drop_last_helper, std::make_index_sequence> {}; template using drop_last_t =3D typename drop_last::type; template struct dropping_invoke_result_helper {}; template struct dropping_invoke_result_helper, T, std::enable_if_t>> { using type =3D std::invoke_result_t; }; template struct dropping_invoke_result_helper, std::index_sequence<0, S...>, std::enable_if_t>> : dropping_invoke_result_helper>...>, std::make_index_sequence> {}; template using dropping_invoke_result =3D dropping_invoke_result_helper, std::index_sequence_for>; template using dropping_invoke_result_t =3D typename dropping_invoke_result::type; template auto dropping_invoke(F&& f, Args&&... args) -> dropping_invoke_result_t= { auto recurse =3D [](auto self) { return [self](auto&&... as) -> decltype(auto) { return self(sel= f, std::forward(as)...); }; }; auto drop =3D recurse([&f](auto self, auto&&... as) -> dropping_invoke_result_t { return apply_sequence([&f, &as..., &self](auto... s) -> decltype(auto) { auto pack =3D std::forward_as_tuple(std::forward(as)...); if constexpr (std::is_invocable_v...>) { return std::invoke( std::forward(f), std::forward>(std::get(std::move(pack)))... ); } else { return self(self, std::forward(f), std::forward>(std::get(std::move(pack)))...); } }); }); return drop(drop, std::forward(args)...); } int main() { dropping_invoke( [](auto a, int b){}, 42.f, 12, 23 ); } I have not succeeded to reduce it more, sorry for the large repro. >>From gcc-bugs-return-609613-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 08:02:13 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 89974 invoked by alias); 11 Jul 2018 08:02:12 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 89546 invoked by uid 48); 11 Jul 2018 08:01:25 -0000 From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/86453] [8/9 Regression] error: type variant differs by TYPE_PACKED in free_lang_data since r255469 Date: Wed, 11 Jul 2018 08:37:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.2 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status component assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00718.txt.bz2 Content-length: 3230 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86453 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Component|lto |c Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot = gnu.org --- Comment #4 from Richard Biener --- Anyhow, fixing the ICE yields: t.ii:2:41: warning: ignoring attribute =E2=80=98packed=E2=80=99 because it = conflicts with attribute =E2=80=98aligned=E2=80=99 [-Wattributes] int *__attribute__((aligned, packed)) a; ^ it looks like ->exclude isn't applied before handle_*. And if I remove aligned then packed flag setting "works", so that is likely the underlying issue. Which means it is a C family / middle-end issue after all. Not sure how to resolve this w/o splitting handlers even more or merging handle_* and exclusion. Martin, you added the exclusion mechanism - we likely ran into this issue before but the exclusion mechanism doesn't "undo" the flag setting effects of the earlier handle_* routines even though it says the attribute is ignor= ed. Note that even with just struct { int *__attribute__((packed)) a; } b; a type variant is built but we do not end up verifying it, it somehow gets collected. This is all a bit confusing but clearly static tree handle_packed_attribute (tree *node, tree name, tree ARG_UNUSED (args), int flags, bool *no_add_attrs) { if (TYPE_P (*node)) { if (!(flags & (int) ATTR_FLAG_TYPE_IN_PLACE)) *node =3D build_variant_type_copy (*node); TYPE_PACKED (*node) =3D 1; } is bogus. Maybe it should really build a distinct type copy here. Maybe the issue is that for ((aligned, packed)) we handle the attributes separate= ly. Given that aligned is documented to not reduce alignment w/o packed when used on structs or struct members it's odd that we diagnose its use on types rather than silently ignoring it: When used on a struct, or struct member, the @code{aligned} attribute can only increase the alignment; in order to decrease it, the @code{packed} attribute must be specified as well. When used as part of a typedef, the @code{aligned} attribute can both increase and decrease alignment, and specifying the @code{packed} attribute generates a warning. I am testing diff --git a/gcc/c-family/c-attribs.c b/gcc/c-family/c-attribs.c index f91add488bb..8cb87eb8154 100644 --- a/gcc/c-family/c-attribs.c +++ b/gcc/c-family/c-attribs.c @@ -502,8 +502,13 @@ handle_packed_attribute (tree *node, tree name, tree ARG_UNUSED (args), if (TYPE_P (*node)) { if (!(flags & (int) ATTR_FLAG_TYPE_IN_PLACE)) - *node =3D build_variant_type_copy (*node); - TYPE_PACKED (*node) =3D 1; + { + warning (OPT_Wattributes, + "%qE attribute ignored for type %qT", name, *node); + *no_add_attrs =3D true; + } + else + TYPE_PACKED (*node) =3D 1; } else if (TREE_CODE (*node) =3D=3D FIELD_DECL) { >>From gcc-bugs-return-609614-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 08:37:45 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 103210 invoked by alias); 11 Jul 2018 08:37:45 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 103145 invoked by uid 48); 11 Jul 2018 08:37:40 -0000 From: "townsend at astro dot wisc.edu" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/86481] New: Memory leak with nested source allocations Date: Wed, 11 Jul 2018 08:39:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 7.2.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: townsend at astro dot wisc.edu X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00719.txt.bz2 Content-length: 2948 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86481 Bug ID: 86481 Summary: Memory leak with nested source allocations Product: gcc Version: 7.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: townsend at astro dot wisc.edu Target Milestone: --- Created attachment 44380 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D44380&action=3Dedit Example program showing the leak I've come across a memory leak with gfortran 7.2.0 (running on Gentoo Linux x86_64), that seems somehow to be related to nested sourced allocations (at least, that's what I've been able to determine). I attach a simple test case that demonstrates the problem. Compile this with gfortran -O2 -g -o simple_leak simple_leak.f90 Then, running valgrind: valgrind --leak-check=3Dfull ./simple_leak ...I get the following output: =3D=3D11555=3D=3D Memcheck, a memory error detector =3D=3D11555=3D=3D Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward = et al. =3D=3D11555=3D=3D Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyr= ight info =3D=3D11555=3D=3D Command: ./simple_leak =3D=3D11555=3D=3D=20 =3D=3D11555=3D=3D=20 =3D=3D11555=3D=3D HEAP SUMMARY: =3D=3D11555=3D=3D in use at exit: 89,600 bytes in 400 blocks =3D=3D11555=3D=3D total heap usage: 515 allocs, 115 frees, 133,468 bytes = allocated =3D=3D11555=3D=3D=20 =3D=3D11555=3D=3D 44,800 (4,800 direct, 40,000 indirect) bytes in 100 block= s are definitely lost in loss record 4 of 4 =3D=3D11555=3D=3D at 0x4C29BFD: malloc (vg_replace_malloc.c:299) =3D=3D11555=3D=3D by 0x4006CC: func_foo (simple_leak.f90:44) =3D=3D11555=3D=3D by 0x4006CC: func_bar (simple_leak.f90:33) =3D=3D11555=3D=3D by 0x4006CC: simple_leak (simple_leak.f90:23) =3D=3D11555=3D=3D by 0x4006CC: main (simple_leak.f90:22) =3D=3D11555=3D=3D=20 =3D=3D11555=3D=3D LEAK SUMMARY: =3D=3D11555=3D=3D definitely lost: 4,800 bytes in 100 blocks =3D=3D11555=3D=3D indirectly lost: 40,000 bytes in 100 blocks =3D=3D11555=3D=3D possibly lost: 0 bytes in 0 blocks =3D=3D11555=3D=3D still reachable: 44,800 bytes in 200 blocks =3D=3D11555=3D=3D suppressed: 0 bytes in 0 blocks =3D=3D11555=3D=3D Reachable blocks (those to which a pointer was found) are= not shown. =3D=3D11555=3D=3D To see them, rerun with: --leak-check=3Dfull --show-leak-= kinds=3Dall =3D=3D11555=3D=3D=20 =3D=3D11555=3D=3D For counts of detected and suppressed errors, rerun with:= -v =3D=3D11555=3D=3D ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 fr= om 0) >>From a bit of playing around, it seems the error may be related to the fact that I'm doing a pair of nested sourced allocations -- one allocation (in func_bar) has an expression for the SOURCE argument that involves a second sourced allocation (in func_foo). cheers, Rich >>From gcc-bugs-return-609615-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 08:39:57 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 11216 invoked by alias); 11 Jul 2018 08:39:57 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 8699 invoked by uid 48); 11 Jul 2018 08:39:53 -0000 From: "kkr at danfoss dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/86482] New: arm vector instruction requiring allignment uses non alligned input Date: Wed, 11 Jul 2018 08:42:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.2.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kkr at danfoss 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: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00720.txt.bz2 Content-length: 2156 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86482 Bug ID: 86482 Summary: arm vector instruction requiring allignment uses non alligned input Product: gcc Version: 7.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: kkr at danfoss dot com Target Milestone: --- See this example on GodBolt: https://godbolt.org/g/DqgXFV This code: struct SomeStruct { SomeStruct(int var1, int var2, int var3, int var4); int var1;=20=20=20=20=20 int var2;=20=20=20 int var3;=20=20=20=20=20=20=20=20=20=20 int var4;=20=20=20=20=20=20 }; SomeStruct::SomeStruct(int var1, int var2, int var3, int var4) : var1(var1) , var2(var2) , var3(var3) , var4(var4) { } With these options: -O3 -mcpu=3Dcortex-a9 -mfpu=3Dneon -mfloat-abi=3Dhard (surprisingly, all of those options are relevant to reproduce the bug, including setting the floating point abi used) Instead of "-O3","-O1 -ftree-vectorize" also produces the guilty assembly instruction. For gcc 7.2.1 for arm, (also reproduced on 7.3.0 and 6.4.1) Produces this assembly: SomeStruct::SomeStruct(int, int, int, int): sub sp, sp, #16 ldr ip, [sp, #16] stm sp, {r1, r2, r3, ip} vld1.64 {d16-d17}, [sp:64] vst1.32 {q8}, [r0] add sp, sp, #16 bx lr As far as i have been able to find, the instruction: vld1.64 {d16-d17}, [sp:64] Requires the input (the stack pointer) to be 64 bit aligned. (the best sour= ce for that i have been able to find, is unfortunately this stack overflow pos= t: https://stackoverflow.com/questions/14708679/alignment-in-vld1 ) But as far as i can see, no such guarantee can be made for the stack pointe= r in this assembly code.=20 Specifically, in our production code, we managed set a break-point on the vld1.64 instruction (vld1.64 {d16,d17},[sp@64]), and at that point in time,= SP was 0x03077B44, actually executing that instruction then generated a "CPU-DATA-ABORT". >>From gcc-bugs-return-609616-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 08:42:56 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 126478 invoked by alias); 11 Jul 2018 08:42:56 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 122248 invoked by uid 48); 11 Jul 2018 08:42:52 -0000 From: "tkoenig at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/86450] Bootstrap failure due to -Wabi Date: Wed, 11 Jul 2018 09:05:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: blocker X-Bugzilla-Who: tkoenig at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00721.txt.bz2 Content-length: 497 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86450 --- Comment #19 from Thomas Koenig --- As a more long-term solution, I think that having -Werror on as the default should actually be preferred, at least for those parts of gcc which are clean at the moment. If somebody then does something which causes a warning to be emitted (either by changing a warning option or by introducing questionable code), the effects would be seen immediately in regression-testing. >>From gcc-bugs-return-609617-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 09:05:18 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 39890 invoked by alias); 11 Jul 2018 09:05:17 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 39837 invoked by uid 48); 11 Jul 2018 09:05:13 -0000 From: "gonzalobg88 at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/86483] New: alloc_size attribute does not work on functions returning a struct that contains the pointer Date: Wed, 11 Jul 2018 09:09: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: gonzalobg88 at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00722.txt.bz2 Content-length: 944 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86483 Bug ID: 86483 Summary: alloc_size attribute does not work on functions returning a struct that contains the pointer Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: gonzalobg88 at gmail dot com Target Milestone: --- I am trying to implementing P0901r0 [0] in jemalloc. The signature of the n= ew memory allocation function looks like this:=20 typedef struct { void *ptr; size_t usize; } smallocx_return_t; smallocx_return_t je_smallocx(size_t size, int flags);=20 I have to set the alloc_size attribute for smallocx_return_t.ptr, but AFAICT this is not currently possible.=20 [0]: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p0901r0.html >>From gcc-bugs-return-609618-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 09:09:00 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 46843 invoked by alias); 11 Jul 2018 09:09:00 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 46795 invoked by uid 48); 11 Jul 2018 09:08:55 -0000 From: "townsend at astro dot wisc.edu" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/86481] Memory leak with nested source allocations Date: Wed, 11 Jul 2018 09:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 7.2.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: townsend at astro dot wisc.edu X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00723.txt.bz2 Content-length: 427 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86481 --- Comment #1 from Rich Townsend --- As addenda: *) I also see the problem on gfortran 8.1 *) It doesn't seem to matter whether bar_t is a subclass of foo_t. This cho= ice was based on the code I developed the test case for, but removing the extends(foo_t) clause from the definition of bar_t leads to the same outcom= e. cheers, Rich >>From gcc-bugs-return-609619-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 09:09:26 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 47834 invoked by alias); 11 Jul 2018 09:09:26 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 47796 invoked by uid 48); 11 Jul 2018 09:09:22 -0000 From: "schwab@linux-m68k.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/86482] arm vector instruction requiring allignment uses non alligned input Date: Wed, 11 Jul 2018 09: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: 7.2.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: schwab@linux-m68k.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00724.txt.bz2 Content-length: 220 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86482 --- Comment #1 from Andreas Schwab --- If you have configured the compiler for the AAPCS ABI then the stack is required to be 64-bit aligned. >>From gcc-bugs-return-609621-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 09:12:07 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 59551 invoked by alias); 11 Jul 2018 09:12:07 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 59499 invoked by uid 48); 11 Jul 2018 09:12:02 -0000 From: "ramana at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/85967] [ARM] No unwinding support for division functions Date: Wed, 11 Jul 2018 09:12:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libgcc X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ramana at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: ramana at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc assigned_to everconfirmed Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00726.txt.bz2 Content-length: 895 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D85967 Ramana Radhakrishnan changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2018-07-11 CC| |ramana at gcc dot gnu.org Assignee|unassigned at gcc dot gnu.org |ramana at gcc dot g= nu.org Ever confirmed|0 |1 --- Comment #3 from Ramana Radhakrishnan --- This patch would fit under the 10 line rule but for the future can I also confirm that you have a copyright assignment in place with the FSF ?=20 It would be good to test this and push this into the tree after a testrun, I can do that for you. Ramana >>From gcc-bugs-return-609620-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 09:10:09 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 55532 invoked by alias); 11 Jul 2018 09:10:09 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 55360 invoked by uid 48); 11 Jul 2018 09:10:00 -0000 From: "gonzalobg88 at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/86483] alloc_size attribute does not work on functions returning a struct that contains the pointer Date: Wed, 11 Jul 2018 09:12:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gonzalobg88 at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00725.txt.bz2 Content-length: 158 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86483 --- Comment #1 from gnzlbg --- The same applies to the malloc attribute. >>From gcc-bugs-return-609622-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 09:12:39 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 60661 invoked by alias); 11 Jul 2018 09:12:38 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 60608 invoked by uid 48); 11 Jul 2018 09:12:34 -0000 From: "ramana at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: =?UTF-8?B?W0J1ZyB0YXJnZXQvODU5MTBdIGNvbmZpZy9hYXJjaDY0L2FhcmNoNjQuYzox?= =?UTF-8?B?NTY1MzoxMjogd2FybmluZzogZHVwbGljYXRlZCDigJhpZuKAmSBjb25kaXRp?= =?UTF-8?B?b24=?= Date: Wed, 11 Jul 2018 09:15:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: 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: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00727.txt.bz2 Content-length: 569 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D85910 Ramana Radhakrishnan changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2018-07-11 CC| |ramana at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from Ramana Radhakrishnan --- Confirmed. >>From gcc-bugs-return-609623-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 09:15:54 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 71392 invoked by alias); 11 Jul 2018 09:15:54 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 70738 invoked by uid 48); 11 Jul 2018 09:15:36 -0000 From: "gonzalobg88 at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/86483] alloc_size attribute does not work on functions returning a struct that contains the pointer Date: Wed, 11 Jul 2018 09:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gonzalobg88 at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00728.txt.bz2 Content-length: 418 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86483 --- Comment #2 from gnzlbg --- The same applies to the alloc_align attribute. It also does not seem possible to specify alloc_align for some flag paramet= er that contains a masked alignment. For example: smallocx_return_t je_smallocx(size_t size, int flags);=20 where the alignment can be specified in some of the bits of flags. >>From gcc-bugs-return-609624-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 09:21:59 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 86912 invoked by alias); 11 Jul 2018 09:21:59 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 86855 invoked by uid 48); 11 Jul 2018 09:21:55 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/86452] ICE in force_decl_die, at dwarf2out.c:25922 with -g1 and -flto Date: Wed, 11 Jul 2018 09:27:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: debug X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00729.txt.bz2 Content-length: 320 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86452 --- Comment #4 from Martin Li=C5=A1ka --- Created attachment 44381 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D44381&action=3Dedit Unreduced test-case Triggered with: $ c++ -g1 -std=3Dc++14 -fPIC -shared -flto=3D9 pr86452.ii >>From gcc-bugs-return-609626-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 09:41:24 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 103772 invoked by alias); 11 Jul 2018 09:41:24 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 103683 invoked by uid 48); 11 Jul 2018 09:41:19 -0000 From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/86461] [9 regression] test case gcc.c-torture/execute/builtins/strlen-3.c fails starting with r262522 Date: Wed, 11 Jul 2018 09:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: testsuite X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org X-Bugzilla-Target-Milestone: 9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: target_milestone Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00731.txt.bz2 Content-length: 293 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86461 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |9.0 >>From gcc-bugs-return-609625-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 09:27:42 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 5638 invoked by alias); 11 Jul 2018 09:27:41 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 4957 invoked by uid 48); 11 Jul 2018 09:27:36 -0000 From: "townsend at astro dot wisc.edu" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/86484] New: Undefined symbol when using polymorphic intrinsic assignment Date: Wed, 11 Jul 2018 09:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 7.2.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: townsend at astro dot wisc.edu X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00730.txt.bz2 Content-length: 1316 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86484 Bug ID: 86484 Summary: Undefined symbol when using polymorphic intrinsic assignment Product: gcc Version: 7.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: townsend at astro dot wisc.edu Target Milestone: --- I'm getting an undefined symbol at link time when compiling the following t= est program, which involves intrinsic polymorphic assignment: program test_assign implicit none type :: foo_t real :: a =3D 1. end type foo_t type, extends (foo_t) :: bar_t real :: b =3D 2. end type bar_t class(foo_t), allocatable :: f type(bar_t) :: b f =3D b print *, f%a end program test_assign =46rom compiling: % gfortran -O2 -o test_assign test_assign.f90 Undefined symbols for architecture x86_64: "___copy_test_assign_Bar_t.3535", referenced from: _MAIN__ in ccPjl5CK.o ___vtab_test_assign_Bar_t.3533 in ccPjl5CK.o ld: symbol(s) not found for architecture x86_64 collect2: error: ld returned 1 exit status This problem seems to exist on both 7.2 and 8.1, and on both Linux and OSX. cheers, Rich >>From gcc-bugs-return-609627-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 09:41:36 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 104616 invoked by alias); 11 Jul 2018 09:41:36 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 104561 invoked by uid 48); 11 Jul 2018 09:41:31 -0000 From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/86462] [9 Regression] Quite huge debug info size increase introduced in r262511 Date: Wed, 11 Jul 2018 09:42:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: debug X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org X-Bugzilla-Target-Milestone: 9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status assigned_to target_milestone Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00732.txt.bz2 Content-length: 525 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86462 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot = gnu.org Target Milestone|--- |9.0 --- Comment #3 from Richard Biener --- I will investigate. >>From gcc-bugs-return-609629-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 09:44:27 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 113703 invoked by alias); 11 Jul 2018 09:44:27 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 113666 invoked by uid 48); 11 Jul 2018 09:44:23 -0000 From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/86467] inlining strcmp with small known length array Date: Wed, 11 Jul 2018 09:44:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: keywords Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00734.txt.bz2 Content-length: 414 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86467 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |missed-optimization --- Comment #1 from Richard Biener --- I think there's a duplicate report. >>From gcc-bugs-return-609628-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 09:42:59 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 107569 invoked by alias); 11 Jul 2018 09:42:59 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 107503 invoked by uid 48); 11 Jul 2018 09:42:55 -0000 From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/86463] Slow compile with -ggdb and optimizations Date: Wed, 11 Jul 2018 09:44:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: debug X-Bugzilla-Version: 8.1.1 X-Bugzilla-Keywords: compile-time-hog 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 version cf_known_to_fail Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00733.txt.bz2 Content-length: 660 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86463 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |compile-time-hog CC| |rguenth at gcc dot gnu.org Component|fortran |debug Version|unknown |8.1.1 Known to fail| |7.2.0, 8.1.1 --- Comment #1 from Richard Biener --- Can you try -ggdb -fno-var-tracking? >>From gcc-bugs-return-609630-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 09:44:39 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 114474 invoked by alias); 11 Jul 2018 09:44:39 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 114397 invoked by uid 48); 11 Jul 2018 09:44:35 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/86450] Bootstrap failure due to -Wabi Date: Wed, 11 Jul 2018 09:45:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: blocker X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-07/txt/msg00735.txt.bz2 Content-length: 643 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86450 --- Comment #20 from Jonathan Wakely --- For libstdc++ the default (without --enable-werror or --disable-werror) is = to add $(WERROR_FLAG) to WARN_FLAGS. WERROR_FLAG is empty by default, but cont= ains -Werror for maintainer mode. So if you use --enable-maintainer-mode --disable-werror then -Werror won't = be added to the libstdc++ flags. Is that an acceptable workaround for now? No code changes required. When I'm back from holiday I'll look into the libstdc++ warning flags and determine why -Wabi was added and how to make it actually work as intended. >>From gcc-bugs-return-609633-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 11 09:46:18 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 117512 invoked by alias); 11 Jul 2018 09:46:18 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 117495 invoked by uid 89); 11 Jul 2018 09:46:17 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-6.9 required=5.0 tests=BAYES_00,GIT_PATCH_2,KAM_SHORT,SPF_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:2331 X-HELO: foss.arm.com Received: from usa-sjc-mx-foss1.foss.arm.com (HELO foss.arm.com) (217.140.101.70) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 11 Jul 2018 09:46:16 +0000 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 8C3E9ED1; Wed, 11 Jul 2018 02:46:14 -0700 (PDT) Received: from e120077-lin.cambridge.arm.com (e120077-lin.cambridge.arm.com [10.2.206.23]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id C03923F318; Wed, 11 Jul 2018 02:46:13 -0700 (PDT) Subject: Re: [Bug target/86383] [9 Regression] arm-netbsdelf cross compiler fails in selftests To: Kamil Rytarowski , "richard.earnshaw at arm dot com" , gcc-bugs@gcc.gnu.org References: <88abee64-0dba-a0f3-3fe6-2f5bc1b48338@gmx.com> From: "Richard Earnshaw (lists)" Openpgp: preference=signencrypt Message-ID: Date: Wed, 11 Jul 2018 09:46:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <88abee64-0dba-a0f3-3fe6-2f5bc1b48338@gmx.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2018-07/txt/msg00738.txt.bz2 Content-length: 2255 On 10/07/18 18:53, Kamil Rytarowski wrote: > On 10.07.2018 19:49, richard.earnshaw at arm dot com wrote: >> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86383 >> >> --- Comment #7 from richard.earnshaw at arm dot com --- >> On 10/07/18 10:57, Kamil Rytarowski wrote: >>> On 06.07.2018 15:26, Richard Earnshaw (lists) wrote: >>>> On 06/07/18 12:11, Kamil Rytarowski wrote: >>>>> On 06.07.2018 12:38, Richard Earnshaw (lists) wrote: >>>>>> On 06/07/18 11:32, Kamil Rytarowski wrote: >>>>>>> On 04.07.2018 20:55, rearnsha at gcc dot gnu.org wrote: >>>>>>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86383 >>>>>>>> >>>>>>>> --- Comment #2 from Richard Earnshaw --- >>>>>>>> I'm not sure how relevant the netbsd-elf port is these days. I believe they've >>>>>>>> now moved onto an EABI based ABI. But no GCC port of that has been >>>>>>>> contributed. >>>>>>>> >>>>>>> >>>>>>> NetBSD switched on newer ARM CPUs to EABI and keeps compat with OABI. A >>>>>>> user is free to build either EABI and OABI for ARMv4+ CPUs. Older pre >>>>>>> ARMv4 CPUs use OABI only. >>>>>>> >>>>>> >>>>>> GCC-9 will drop support for pre-armv4 CPUs. Such support has been >>>>>> marked as deprecated for about 3 years now. >>>>>> >>>>> >>>>> We verify these ports on real hardware. >>>>> >>>>> NetBSD/shark is prepared to be switched to Clang/LLVM as GCC is >>>>> obsoleting it and surprisingly LLVM soon might have support for a wider >>>>> range of ARM CPUs. >>>>> >>>> >>>> Shark's use strongARM cpus, which are ARMv4. That's not been obsoleted, >>>> but it is considered deprecated these days. >>>> >>> >>> Shark doesn't use all instructions that are generated by GCC (I forgot >>> the CPU property name of it) and thus it has to be switched to Clang/LLVM. >>> >> >> You're not making sense. Please be more explicit as to what you mean >> and give an example. GCC can generate instructions for ARMv4 and >> StrongARM (used by the shark) is an ARMv4 part. >> >> I've run gcc generated code on shark boards for years and not seen problems. >> >> R. >> > > I got a feedback that it's called: armv4t. > >>From whom? StrongARM is ARMv4. It is *not* ARMv4t as it does not support Thumb. Whatever, GCC can support both ARMv4 and ARMv4t. R.