From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12179 invoked by alias); 10 Jul 2017 17:56: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 Received: (qmail 5510 invoked by uid 48); 10 Jul 2017 17:56:18 -0000 From: "jeff.science at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/81358] libatomic not automatically linked with C11 code Date: Mon, 10 Jul 2017 17:56:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: driver X-Bugzilla-Version: 7.1.1 X-Bugzilla-Keywords: link-failure X-Bugzilla-Severity: normal X-Bugzilla-Who: jeff.science at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: 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: 2017-07/txt/msg00841.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81358 --- Comment #5 from Jeff Hammond --- Indeed, _Atomic is a language keyword and doesn't require any headers (the inclusion of stdatomic.h in this code is superfluous), so the "header->expl= icit library" argument doesn't apply. In any case, I do not see why language intrinsics that require headers shou= ld require libraries. Why is sqrt() from math.h different from fprintf() from stdio.h? Maybe POSIX requires that, but ISO C11 doesn't, and I'm using -std=3Dc11 not -std=3Dposix. --as-needed would greatly enhance user experience for both this and libm. >>From gcc-bugs-return-568292-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 10 17:59:48 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 23379 invoked by alias); 10 Jul 2017 17:59: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 22812 invoked by uid 55); 10 Jul 2017 17:59:34 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/81381] std::basic_stringbuf only works with DefaultConstructible allocators Date: Mon, 10 Jul 2017 17: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: 8.0 X-Bugzilla-Keywords: rejects-valid X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: redi at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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: 2017-07/txt/msg00843.txt.bz2 Content-length: 840 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81381 --- Comment #1 from Jonathan Wakely --- Author: redi Date: Mon Jul 10 17:59:02 2017 New Revision: 250101 URL: https://gcc.gnu.org/viewcvs?rev=3D250101&root=3Dgcc&view=3Drev Log: PR libstdc++/81381 support stateful allocators in basic_stringbuf PR libstdc++/81381 * include/bits/sstream.tcc (basic_stringbuf::overflow) (basic_stringbuf::basic_stringbuf(const __string_type&, ios::mode)) (basic_stringbuf::str()): Construct new strings with an allocator. * testsuite/27_io/basic_stringbuf/cons/81381.cc: New. Added: trunk/libstdc++-v3/testsuite/27_io/basic_stringbuf/cons/81381.cc Modified: trunk/libstdc++-v3/ChangeLog trunk/libstdc++-v3/include/bits/sstream.tcc trunk/libstdc++-v3/include/std/sstream >>From gcc-bugs-return-568291-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 10 17:59:33 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 22543 invoked by alias); 10 Jul 2017 17:59: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 22462 invoked by uid 55); 10 Jul 2017 17:59:28 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/81338] stringstream remains empty after being moved into multiple times Date: Mon, 10 Jul 2017 17: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: 6.3.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: redi at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: 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: 2017-07/txt/msg00842.txt.bz2 Content-length: 1054 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81338 --- Comment #2 from Jonathan Wakely --- Author: redi Date: Mon Jul 10 17:58:56 2017 New Revision: 250100 URL: https://gcc.gnu.org/viewcvs?rev=3D250100&root=3Dgcc&view=3Drev Log: PR libstdc++/81338 correctly manage string capacity PR libstdc++/81338 * include/bits/basic_string.h [_GLIBCXX_USE_CXX11_ABI] (basic_strin= g): Declare basic_stringbuf to be a friend. * include/bits/sstream.tcc (basic_stringbuf::overflow) [_GLIBCXX_USE_CXX11_ABI]: Use unused capacity before reallocating. * include/std/sstream (basic_stringbuf::__xfer_bufptrs): Update str= ing length to buffer length. * testsuite/27_io/basic_stringstream/assign/81338.cc: New. Added: trunk/libstdc++-v3/testsuite/27_io/basic_stringstream/assign/81338.cc Modified: trunk/libstdc++-v3/ChangeLog trunk/libstdc++-v3/include/bits/basic_string.h trunk/libstdc++-v3/include/bits/sstream.tcc trunk/libstdc++-v3/include/std/sstream >>From gcc-bugs-return-568293-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 10 18:07:22 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 107197 invoked by alias); 10 Jul 2017 18:07:21 -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 101504 invoked by uid 48); 10 Jul 2017 18:07:16 -0000 From: "msebor at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81384] New: built-in form of strnlen missing Date: Mon, 10 Jul 2017 18:07:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: msebor at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-07/txt/msg00844.txt.bz2 Content-length: 1544 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81384 Bug ID: 81384 Summary: built-in form of strnlen missing Product: gcc Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: msebor at gcc dot gnu.org Target Milestone: --- GCC doesn't provide a built-in form of the POSIX strnlen function. Providi= ng such a built-in would make it possible to emit more efficient code for prog= rams that make use of it. The Linux kernel, for example, has on the order of 260 instances of calls to strnlen. The test case below shows one instance of a missed optimization opportunity involving strnlen. $ cat b.c && gcc -O2 -S -Wall -Wextra -fdump-tree-optimized=3D/dev/stdout b= .c typedef __SIZE_TYPE__ size_t; size_t strnlen (const char*, size_t); void f (const char *s) { unsigned n =3D strnlen (s, 7); if (n > 7) // can never hold __builtin_abort (); // can be eliminated } ;; Function f (f, funcdef_no=3D0, decl_uid=3D1819, cgraph_uid=3D0, symbol_o= rder=3D0) f (const char * s) { unsigned int n; long unsigned int _1; [100.00%] [count: INV]: _1 =3D strnlen (s_3(D), 7); n_5 =3D (unsigned int) _1; if (n_5 > 7) goto ; [0.04%] [count: 0] else goto ; [99.96%] [count: INV] [0.04%] [count: 0]: __builtin_abort (); [99.96%] [count: INV]: return; } >>From gcc-bugs-return-568294-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 10 18:17:10 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 121934 invoked by alias); 10 Jul 2017 18:17:10 -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 121873 invoked by uid 48); 10 Jul 2017 18:17:05 -0000 From: "msebor at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81385] New: missing optimization involving strlen of arrays of known size Date: Mon, 10 Jul 2017 18:17:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: msebor at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-07/txt/msg00845.txt.bz2 Content-length: 2199 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81385 Bug ID: 81385 Summary: missing optimization involving strlen of arrays of known size Product: gcc Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: msebor at gcc dot gnu.org Target Milestone: --- A valid argument to the strlen() function that is an array of known size (or that points to one) must contain a string whose length is less than the arr= ay size. It is possible to rely on this guarantee to emit more efficient code than without it. The test case below shows that GCC doesn't take advantage= of this optimization opportunity. $ cat b.c && gcc -O2 -S -Wall -Wextra -fdump-tree-optimized=3D/dev/stdout b= .c typedef __SIZE_TYPE__ size_t; size_t strlen (const char*); char a[7]; void f (void) { unsigned n =3D strlen (a); if (n >=3D sizeof a) // can never hold __builtin_abort (); // can be eliminated } struct S { char a[7]; int i; }; void g (const struct S *s) { unsigned n =3D strlen (s->a); if (n >=3D sizeof s->a) // can never hold __builtin_abort (); // can be eliminated } ;; Function f (f, funcdef_no=3D0, decl_uid=3D1819, cgraph_uid=3D0, symbol_o= rder=3D1) f () { unsigned int n; long unsigned int _1; [100.00%] [count: INV]: _1 =3D strlen (&a); n_3 =3D (unsigned int) _1; if (n_3 > 6) goto ; [0.04%] [count: 0] else goto ; [99.96%] [count: INV] [0.04%] [count: 0]: __builtin_abort (); [99.96%] [count: INV]: return; } ;; Function g (g, funcdef_no=3D1, decl_uid=3D1826, cgraph_uid=3D1, symbol_o= rder=3D2) g (const struct S * s) { unsigned int n; const char[7] * _1; long unsigned int _2; [100.00%] [count: INV]: _1 =3D &s_3(D)->a; _2 =3D strlen (_1); n_5 =3D (unsigned int) _2; if (n_5 > 6) goto ; [0.04%] [count: 0] else goto ; [99.96%] [count: INV] [0.04%] [count: 0]: __builtin_abort (); [99.96%] [count: INV]: return; } >>From gcc-bugs-return-568295-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 10 18:18:34 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 123541 invoked by alias); 10 Jul 2017 18:18:34 -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 123471 invoked by uid 48); 10 Jul 2017 18:18:29 -0000 From: "msebor at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81385] missing optimization involving strlen of arrays of known size Date: Mon, 10 Jul 2017 18:18:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: msebor at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: keywords see_also 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: 2017-07/txt/msg00846.txt.bz2 Content-length: 647 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81385 Martin Sebor changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |missed-optimization See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=3D81384 --- Comment #1 from Martin Sebor --- The same opportunity exists for the strnlen function (bug 81384 is an enhancement request to provide a builtin-in for it). >>From gcc-bugs-return-568296-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 10 18:18:53 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 124456 invoked by alias); 10 Jul 2017 18:18:49 -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 124386 invoked by uid 48); 10 Jul 2017 18:18:43 -0000 From: "msebor at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81384] built-in form of strnlen missing Date: Mon, 10 Jul 2017 18:18:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: enhancement X-Bugzilla-Who: msebor at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_severity 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: 2017-07/txt/msg00847.txt.bz2 Content-length: 298 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81384 Martin Sebor changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |enhancement >>From gcc-bugs-return-568297-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 10 19:35:06 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 80518 invoked by alias); 10 Jul 2017 19:35:05 -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 79891 invoked by uid 48); 10 Jul 2017 19:34:59 -0000 From: "hjl.tools at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/81383] -fstack-protector doesn't work well Date: Mon, 10 Jul 2017 19:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libgcc X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hjl.tools at gmail dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WONTFIX X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: 2017-07/txt/msg00848.txt.bz2 Content-length: 491 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81383 H.J. Lu changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |WONTFIX --- Comment #5 from H.J. Lu --- Will fix glibc instead: https://sourceware.org/bugzilla/show_bug.cgi?id=3D12189 >>From gcc-bugs-return-568298-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 10 19:44:28 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 99932 invoked by alias); 10 Jul 2017 19: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 99663 invoked by uid 48); 10 Jul 2017 19:44:19 -0000 From: "ubizjak at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/81375] [6/7/8 Regression] unrecognizable insn Date: Mon, 10 Jul 2017 19:44:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 7.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ubizjak at gmail dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: ubizjak at gmail dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed 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: 2017-07/txt/msg00849.txt.bz2 Content-length: 695 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81375 Uro=C5=A1 Bizjak changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2017-07-10 Assignee|unassigned at gcc dot gnu.org |ubizjak at gmail do= t com Ever confirmed|0 |1 --- Comment #1 from Uro=C5=A1 Bizjak --- Created attachment 41710 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D41710&action=3Dedit Proposed patch Patch in testing. >>From gcc-bugs-return-568299-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 10 19:45:48 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 102797 invoked by alias); 10 Jul 2017 19:45: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 101901 invoked by uid 48); 10 Jul 2017 19:45:02 -0000 From: "ubizjak at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/81375] [6/7/8 Regression] unrecognizable insn Date: Mon, 10 Jul 2017 19:45:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 7.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ubizjak at gmail dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: ubizjak at gmail dot com X-Bugzilla-Target-Milestone: 6.5 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cf_gcctarget cf_gcchost target_milestone 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: 2017-07/txt/msg00850.txt.bz2 Content-length: 449 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81375 Uro=C5=A1 Bizjak changed: What |Removed |Added ---------------------------------------------------------------------------- Target|x86_64-linux-gnu |x86_32 Host|x86_64-linux-gnu | Target Milestone|--- |6.5 Build|x86_64-linux-gnu | >>From gcc-bugs-return-568300-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 10 20:02:30 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 82761 invoked by alias); 10 Jul 2017 20:02:30 -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 82506 invoked by uid 55); 10 Jul 2017 20:02:25 -0000 From: "joseph at codesourcery dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/81358] libatomic not automatically linked with C11 code Date: Mon, 10 Jul 2017 20:02:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: driver X-Bugzilla-Version: 7.1.1 X-Bugzilla-Keywords: link-failure X-Bugzilla-Severity: normal X-Bugzilla-Who: joseph at codesourcery dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: 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: 2017-07/txt/msg00851.txt.bz2 Content-length: 1133 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81358 --- Comment #6 from joseph at codesourcery dot com --- The design of what's in separate libraries is historical; since it=20 probably predates shared libraries, the reason isn't obvious (with shared=20 libraries, before --as-needed, it avoided unnecessary runtime=20 dependencies). The conformance documentation for an implementation as a=20 whole (compiler plus libraries) would of course specify using -std=3Dc11=20 -pedantic -lm -latomic, or whatever. For a new libc implementation for=20 Unix-like systems it would be natural just to use libc.so for everything,=20 subject to performance issues from causing everything to be (potentially)=20 multithreaded by linking with pthreads functions. Note e.g. glibc moved=20 some clock/timer functions from librt to libc a while back to avoid such=20 issues from linking in librt. The POSIX rules for the c99 utility, which correspond more or less to the=20 traditional division into libraries on Unix-like systems, are at:=20 http://pubs.opengroup.org/onlinepubs/9699919799/utilities/c99.html >>From gcc-bugs-return-568301-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 10 20:25:13 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 44985 invoked by alias); 10 Jul 2017 20:25: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 44057 invoked by uid 48); 10 Jul 2017 20:25:04 -0000 From: "seurer at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/81386] New: [8 regression] libgomp.fortran/appendix-a/a.16.1.f90 fails starting with 249424 Date: Mon, 10 Jul 2017 20:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libgomp X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: seurer at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc 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: 2017-07/txt/msg00852.txt.bz2 Content-length: 28523 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81386 Bug ID: 81386 Summary: [8 regression] libgomp.fortran/appendix-a/a.16.1.f90 fails starting with 249424 Product: gcc Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libgomp Assignee: unassigned at gcc dot gnu.org Reporter: seurer at gcc dot gnu.org CC: jakub at gcc dot gnu.org Target Milestone: --- These were run on a power8 LE machine. The compiled code works fine if -fopenmp is left off the compilation comman= d. A failure is still occurring now (see further down) but is a bit different.= =20 Here is with r249424: seurer@genoa:~/gcc/build/gcc-test$ /home/seurer/gcc/build/gcc-test/gcc/xgcc -B/home/seurer/gcc/build/gcc-test/gcc/ /home/seurer/gcc/gcc-test/libgomp/testsuite/libgomp.fortran/appendix-a/a.16= .1.f90 -B/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp/ -B/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp/.= libs -I/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp -I/home/seurer/gcc/gcc-test/libgomp/testsuite/../../include -I/home/seurer/gcc/gcc-test/libgomp/testsuite/.. -fmessage-length=3D0 -fno-diagnostics-show-caret -Wno-hsa -fdiagnostics-color=3Dnever -fopenmp -= O3 -g -B/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp/.= ./libgfortran/.libs -fintrinsic-modules-path=3D/home/seurer/gcc/build/gcc-test/powerpc64le-unkn= own-linux-gnu/./libgomp -L/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp/.= libs -L/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp/.= ./libgfortran/.libs -lgfortran -foffload=3D-lgfortran -lm -o ./a.16.1.exe seurer@genoa:~/gcc/build/gcc-test$ ./a.16.1.exe=20 Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Backtrace for this error: Backtrace for this error: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: Backtrace for this error: #0 0x3fffa47e9a9f in ??? Segmentation fault (core dumped) seurer@genoa:~/gcc/build/gcc-test$ gdb ./a.16.1.exe=20 GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1 . . . Reading symbols from ./a.16.1.exe...done. (gdb) run Starting program: /home/seurer/gcc/build/gcc-test/a.16.1.exe=20 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/powerpc64le-linux-gnu/libthread_db.so= .1". [New Thread 0x3fffb78af130 (LWP 118972)] [New Thread 0x3fffb70af130 (LWP 118980)] [New Thread 0x3fffb68af130 (LWP 118982)] [New Thread 0x3fffb60af130 (LWP 118986)] [New Thread 0x3fffb58af130 (LWP 118988)] [New Thread 0x3fffb50af130 (LWP 118991)] [New Thread 0x3fffb48af130 (LWP 118993)] [New Thread 0x3fffb40af130 (LWP 118995)] [New Thread 0x3fffb38af130 (LWP 118997)] [New Thread 0x3fffb30af130 (LWP 119000)] [New Thread 0x3fffb28af130 (LWP 119001)] [New Thread 0x3fffb20af130 (LWP 119003)] [New Thread 0x3fffb18af130 (LWP 119007)] [New Thread 0x3fffb10af130 (LWP 119008)] [New Thread 0x3fffb08af130 (LWP 119010)] [New Thread 0x3fffb00af130 (LWP 119014)] [New Thread 0x3fffaf8af130 (LWP 119016)] [New Thread 0x3fffaf0af130 (LWP 119019)] [New Thread 0x3fffae8af130 (LWP 119021)] [New Thread 0x3fffae0af130 (LWP 119023)] [New Thread 0x3fffad8af130 (LWP 119027)] [New Thread 0x3fffad0af130 (LWP 119028)] [New Thread 0x3fffac8af130 (LWP 119030)] [New Thread 0x3fffac0af130 (LWP 119034)] [New Thread 0x3fffab8af130 (LWP 119036)] [New Thread 0x3fffab0af130 (LWP 119039)] [New Thread 0x3fffaa8af130 (LWP 119041)] [New Thread 0x3fffaa0af130 (LWP 119043)] [New Thread 0x3fffa98af130 (LWP 119047)] [New Thread 0x3fffa90af130 (LWP 119049)] [New Thread 0x3fffa88af130 (LWP 119053)] [New Thread 0x3fffa80af130 (LWP 119054)] [New Thread 0x3fffa78af130 (LWP 119056)] [New Thread 0x3fffa70af130 (LWP 119060)] [New Thread 0x3fffa68af130 (LWP 119062)] [New Thread 0x3fffa60af130 (LWP 119067)] [New Thread 0x3fffa58af130 (LWP 119069)] [New Thread 0x3fffa50af130 (LWP 119073)] [New Thread 0x3fffa48af130 (LWP 119074)] [New Thread 0x3fffa40af130 (LWP 119077)] [New Thread 0x3fffa38af130 (LWP 119080)] [New Thread 0x3fffa30af130 (LWP 119082)] [New Thread 0x3fffa28af130 (LWP 119086)] [New Thread 0x3fffa20af130 (LWP 119088)] [New Thread 0x3fffa18af130 (LWP 119092)] [New Thread 0x3fffa10af130 (LWP 119094)] [New Thread 0x3fffa08af130 (LWP 119098)] [New Thread 0x3fffa00af130 (LWP 119100)] [New Thread 0x3fff9f8af130 (LWP 119104)] [New Thread 0x3fff9f0af130 (LWP 119105)] [New Thread 0x3fff9e8af130 (LWP 119108)] [New Thread 0x3fff9e0af130 (LWP 119111)] [New Thread 0x3fff9d8af130 (LWP 119113)] [New Thread 0x3fff9d0af130 (LWP 119117)] [New Thread 0x3fff9c8af130 (LWP 119119)] [New Thread 0x3fff9c0af130 (LWP 119124)] [New Thread 0x3fff9b8af130 (LWP 119126)] [New Thread 0x3fff9b0af130 (LWP 119130)] [New Thread 0x3fff9a8af130 (LWP 119132)] [New Thread 0x3fff9a0af130 (LWP 119136)] [New Thread 0x3fff998af130 (LWP 119138)] [New Thread 0x3fff990af130 (LWP 119142)] [New Thread 0x3fff988af130 (LWP 119144)] [New Thread 0x3fff980af130 (LWP 119146)] [New Thread 0x3fff978af130 (LWP 119148)] [New Thread 0x3fff970af130 (LWP 119151)] [New Thread 0x3fff968af130 (LWP 119156)] [New Thread 0x3fff960af130 (LWP 119158)] [New Thread 0x3fff958af130 (LWP 119162)] [New Thread 0x3fff950af130 (LWP 119164)] [New Thread 0x3fff948af130 (LWP 119168)] [New Thread 0x3fff940af130 (LWP 119172)] [New Thread 0x3fff938af130 (LWP 119175)] [New Thread 0x3fff930af130 (LWP 119179)] [New Thread 0x3fff928af130 (LWP 119182)] [New Thread 0x3fff920af130 (LWP 119201)] [New Thread 0x3fff918af130 (LWP 119204)] [New Thread 0x3fff910af130 (LWP 119206)] [New Thread 0x3fff908af130 (LWP 119207)] [New Thread 0x3fff900af130 (LWP 119208)] [New Thread 0x3fff8f8af130 (LWP 119209)] [New Thread 0x3fff8f0af130 (LWP 119212)] [New Thread 0x3fff8e8af130 (LWP 119215)] [New Thread 0x3fff8e0af130 (LWP 119218)] [New Thread 0x3fff8d8af130 (LWP 119223)] [New Thread 0x3fff8d0af130 (LWP 119225)] [New Thread 0x3fff8c8af130 (LWP 119229)] [New Thread 0x3fff8c0af130 (LWP 119234)] [New Thread 0x3fff8b8af130 (LWP 119236)] [New Thread 0x3fff8b0af130 (LWP 119240)] [New Thread 0x3fff8a8af130 (LWP 119245)] [New Thread 0x3fff8a0af130 (LWP 119247)] [New Thread 0x3fff898af130 (LWP 119251)] [New Thread 0x3fff890af130 (LWP 119254)] [New Thread 0x3fff888af130 (LWP 119257)] [New Thread 0x3fff880af130 (LWP 119262)] [New Thread 0x3fff878af130 (LWP 119264)] [New Thread 0x3fff870af130 (LWP 119268)] [New Thread 0x3fff868af130 (LWP 119271)] [New Thread 0x3fff860af130 (LWP 119273)] [New Thread 0x3fff858af130 (LWP 119275)] [New Thread 0x3fff850af130 (LWP 119276)] [New Thread 0x3fff848af130 (LWP 119278)] [New Thread 0x3fff840af130 (LWP 119280)] [New Thread 0x3fff838af130 (LWP 119281)] [New Thread 0x3fff830af130 (LWP 119282)] [New Thread 0x3fff828af130 (LWP 119283)] [New Thread 0x3fff820af130 (LWP 119285)] [New Thread 0x3fff818af130 (LWP 119287)] [New Thread 0x3fff810af130 (LWP 119289)] [New Thread 0x3fff808af130 (LWP 119292)] [New Thread 0x3fff800af130 (LWP 119294)] [New Thread 0x3fff7f8af130 (LWP 119296)] [New Thread 0x3fff7f0af130 (LWP 119299)] [New Thread 0x3fff7e8af130 (LWP 119300)] [New Thread 0x3fff7e0af130 (LWP 119303)] [New Thread 0x3fff7d8af130 (LWP 119305)] [New Thread 0x3fff7d0af130 (LWP 119307)] [New Thread 0x3fff7c8af130 (LWP 119309)] [New Thread 0x3fff7c0af130 (LWP 119312)] [New Thread 0x3fff7b8af130 (LWP 119313)] [New Thread 0x3fff7b0af130 (LWP 119315)] [New Thread 0x3fff7a8af130 (LWP 119318)] [New Thread 0x3fff7a0af130 (LWP 119320)] [New Thread 0x3fff798af130 (LWP 119321)] [New Thread 0x3fff790af130 (LWP 119322)] [New Thread 0x3fff788af130 (LWP 119323)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x3fff788af130 (LWP 119323)] 0x0000000010000b78 in suba16_._omp_fn.0 () at /home/seurer/gcc/gcc-test/libgomp/testsuite/libgomp.fortran/appendix-a/a.16= .1.f90:20 20 !$OMP ATOMIC (gdb) where #0 0x0000000010000b78 in suba16_._omp_fn.0 () at /home/seurer/gcc/gcc-test/libgomp/testsuite/libgomp.fortran/appendix-a/a.16= .1.f90:20 #1 0x00003fffb7b1f640 in gomp_thread_start () from /home/seurer/gcc/install/gcc-7.1.0/lib64/libgomp.so.1 #2 0x00003fffb7ad89d8 in start_thread (arg=3D0x3fff788af130) at pthread_create.c:314 #3 0x00003fffb7a2ef00 in clone () at ../sysdeps/unix/sysv/linux/powerpc/powerpc64/clone.S:104 This trace is with r250099: seurer@genoa:~/gcc/build/gcc-test2$ /home/seurer/gcc/build/gcc-test2/gcc/xg= cc -B/home/seurer/gcc/build/gcc-test2/gcc/ /home/seurer/gcc/gcc-test2/libgomp/testsuite/libgomp.fortran/appendix-a/a.1= 6.1.f90 -B/home/seurer/gcc/build/gcc-test2/powerpc64le-unknown-linux-gnu/./libgomp/ -B/home/seurer/gcc/build/gcc-test2/powerpc64le-unknown-linux-gnu/./libgomp/= .libs -I/home/seurer/gcc/build/gcc-test2/powerpc64le-unknown-linux-gnu/./libgomp -I/home/seurer/gcc/gcc-test2/libgomp/testsuite/../../include -I/home/seurer/gcc/gcc-test2/libgomp/testsuite/.. -fmessage-length=3D0 -fno-diagnostics-show-caret -Wno-hsa -fdiagnostics-color=3Dnever -fopenmp -= O3 -g -B/home/seurer/gcc/build/gcc-test2/powerpc64le-unknown-linux-gnu/./libgomp/= ../libgfortran/.libs -fintrinsic-modules-path=3D/home/seurer/gcc/build/gcc-test2/powerpc64le-unk= nown-linux-gnu/./libgomp -L/home/seurer/gcc/build/gcc-test2/powerpc64le-unknown-linux-gnu/./libgomp/= .libs -L/home/seurer/gcc/build/gcc-test2/powerpc64le-unknown-linux-gnu/./libgomp/= ../libgfortran/.libs -lgfortran -foffload=3D-lgfortran -lm -o ./a.16.1.exe seurer@genoa:~/gcc/build/gcc-test2$ ./a.16.1.exe=20 Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: #0 0x3fff82ad9a9f in ??? Segmentation fault (core dumped) seurer@genoa:~/gcc/build/gcc-test2$ gdb a.16.1.exe=20 GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1 . . . Reading symbols from a.16.1.exe...done. (gdb) run Starting program: /home/seurer/gcc/build/gcc-test2/a.16.1.exe=20 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/powerpc64le-linux-gnu/libthread_db.so= .1". [New Thread 0x3fffb78af130 (LWP 78484)] [New Thread 0x3fffb70af130 (LWP 78516)] [New Thread 0x3fffb68af130 (LWP 78517)] [New Thread 0x3fffb60af130 (LWP 78521)] [New Thread 0x3fffb58af130 (LWP 78524)] [New Thread 0x3fffb50af130 (LWP 78525)] [New Thread 0x3fffb48af130 (LWP 78535)] [New Thread 0x3fffb40af130 (LWP 78546)] [New Thread 0x3fffb38af130 (LWP 78553)] [New Thread 0x3fffb30af130 (LWP 78556)] [New Thread 0x3fffb28af130 (LWP 78561)] [New Thread 0x3fffb20af130 (LWP 78564)] [New Thread 0x3fffb18af130 (LWP 78567)] [New Thread 0x3fffb10af130 (LWP 78570)] [New Thread 0x3fffb08af130 (LWP 78578)] [New Thread 0x3fffb00af130 (LWP 78584)] [New Thread 0x3fffaf8af130 (LWP 78587)] [New Thread 0x3fffaf0af130 (LWP 78590)] [New Thread 0x3fffae8af130 (LWP 78593)] [New Thread 0x3fffae0af130 (LWP 78596)] [New Thread 0x3fffad8af130 (LWP 78599)] [New Thread 0x3fffad0af130 (LWP 78603)] [New Thread 0x3fffac8af130 (LWP 78604)] [New Thread 0x3fffac0af130 (LWP 78607)] [New Thread 0x3fffab8af130 (LWP 78610)] [New Thread 0x3fffab0af130 (LWP 78612)] [New Thread 0x3fffaa8af130 (LWP 78613)] [New Thread 0x3fffaa0af130 (LWP 78614)] [New Thread 0x3fffa98af130 (LWP 78617)] [New Thread 0x3fffa90af130 (LWP 78622)] [New Thread 0x3fffa88af130 (LWP 78624)] [New Thread 0x3fffa80af130 (LWP 78626)] [New Thread 0x3fffa78af130 (LWP 78629)] [New Thread 0x3fffa70af130 (LWP 78634)] [New Thread 0x3fffa68af130 (LWP 78637)] [New Thread 0x3fffa60af130 (LWP 78641)] [New Thread 0x3fffa58af130 (LWP 78643)] [New Thread 0x3fffa50af130 (LWP 78647)] [New Thread 0x3fffa48af130 (LWP 78653)] [New Thread 0x3fffa40af130 (LWP 78657)] [New Thread 0x3fffa38af130 (LWP 78659)] [New Thread 0x3fffa30af130 (LWP 78662)] [New Thread 0x3fffa28af130 (LWP 78665)] [New Thread 0x3fffa20af130 (LWP 78670)] [New Thread 0x3fffa18af130 (LWP 78672)] [New Thread 0x3fffa10af130 (LWP 78674)] [New Thread 0x3fffa08af130 (LWP 78676)] [New Thread 0x3fffa00af130 (LWP 78682)] [New Thread 0x3fff9f8af130 (LWP 78686)] [New Thread 0x3fff9f0af130 (LWP 78690)] [New Thread 0x3fff9e8af130 (LWP 78699)] [New Thread 0x3fff9e0af130 (LWP 78705)] [New Thread 0x3fff9d8af130 (LWP 78708)] [New Thread 0x3fff9d0af130 (LWP 78715)] [New Thread 0x3fff9c8af130 (LWP 78717)] [New Thread 0x3fff9c0af130 (LWP 78726)] [New Thread 0x3fff9b8af130 (LWP 78731)] [New Thread 0x3fff9b0af130 (LWP 78736)] [New Thread 0x3fff9a8af130 (LWP 78743)] [New Thread 0x3fff9a0af130 (LWP 78747)] [New Thread 0x3fff998af130 (LWP 78748)] [New Thread 0x3fff990af130 (LWP 78753)] [New Thread 0x3fff988af130 (LWP 78755)] [New Thread 0x3fff980af130 (LWP 78760)] [New Thread 0x3fff978af130 (LWP 78764)] [New Thread 0x3fff970af130 (LWP 78768)] [New Thread 0x3fff968af130 (LWP 78771)] [New Thread 0x3fff960af130 (LWP 78774)] [New Thread 0x3fff958af130 (LWP 78778)] [New Thread 0x3fff950af130 (LWP 78779)] [New Thread 0x3fff948af130 (LWP 78786)] [New Thread 0x3fff940af130 (LWP 78788)] [New Thread 0x3fff938af130 (LWP 78792)] [New Thread 0x3fff930af130 (LWP 78800)] [New Thread 0x3fff928af130 (LWP 78803)] [New Thread 0x3fff920af130 (LWP 78807)] [New Thread 0x3fff918af130 (LWP 78811)] [New Thread 0x3fff910af130 (LWP 78818)] [New Thread 0x3fff908af130 (LWP 78822)] [New Thread 0x3fff900af130 (LWP 78827)] [New Thread 0x3fff8f8af130 (LWP 78829)] [New Thread 0x3fff8f0af130 (LWP 78835)] [New Thread 0x3fff8e8af130 (LWP 78840)] [New Thread 0x3fff8e0af130 (LWP 78843)] [New Thread 0x3fff8d8af130 (LWP 78847)] [New Thread 0x3fff8d0af130 (LWP 78853)] [New Thread 0x3fff8c8af130 (LWP 78855)] [New Thread 0x3fff8c0af130 (LWP 78857)] [New Thread 0x3fff8b8af130 (LWP 78863)] [New Thread 0x3fff8b0af130 (LWP 78866)] [New Thread 0x3fff8a8af130 (LWP 78868)] [New Thread 0x3fff8a0af130 (LWP 78874)] [New Thread 0x3fff898af130 (LWP 78886)] [New Thread 0x3fff890af130 (LWP 78890)] [New Thread 0x3fff888af130 (LWP 78896)] [New Thread 0x3fff880af130 (LWP 78899)] [New Thread 0x3fff878af130 (LWP 78910)] [New Thread 0x3fff870af130 (LWP 78918)] [New Thread 0x3fff868af130 (LWP 78923)] [New Thread 0x3fff860af130 (LWP 78931)] [New Thread 0x3fff858af130 (LWP 78934)] [New Thread 0x3fff850af130 (LWP 78944)] [New Thread 0x3fff848af130 (LWP 78950)] [New Thread 0x3fff840af130 (LWP 78955)] [New Thread 0x3fff838af130 (LWP 78960)] [New Thread 0x3fff830af130 (LWP 78971)] [New Thread 0x3fff828af130 (LWP 78986)] [New Thread 0x3fff820af130 (LWP 78992)] [New Thread 0x3fff818af130 (LWP 78999)] [New Thread 0x3fff810af130 (LWP 79003)] [New Thread 0x3fff808af130 (LWP 79007)] [New Thread 0x3fff800af130 (LWP 79012)] [New Thread 0x3fff7f8af130 (LWP 79015)] [New Thread 0x3fff7f0af130 (LWP 79032)] [New Thread 0x3fff7e8af130 (LWP 79036)] [New Thread 0x3fff7e0af130 (LWP 79043)] [New Thread 0x3fff7d8af130 (LWP 79051)] [New Thread 0x3fff7d0af130 (LWP 79053)] [New Thread 0x3fff7c8af130 (LWP 79060)] [New Thread 0x3fff7c0af130 (LWP 79082)] [New Thread 0x3fff7b8af130 (LWP 79089)] [New Thread 0x3fff7b0af130 (LWP 79093)] [New Thread 0x3fff7a8af130 (LWP 79101)] [New Thread 0x3fff7a0af130 (LWP 79109)] [New Thread 0x3fff798af130 (LWP 79116)] [New Thread 0x3fff790af130 (LWP 79123)] [New Thread 0x3fff788af130 (LWP 79125)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x3fff788af130 (LWP 79125)] 0x0000000010000b78 in suba16_._omp_fn.0 () at /home/seurer/gcc/gcc-test2/libgomp/testsuite/libgomp.fortran/appendix-a/a.1= 6.1.f90:20 20 !$OMP ATOMIC (gdb) where #0 0x0000000010000b78 in suba16_._omp_fn.0 () at /home/seurer/gcc/gcc-test2/libgomp/testsuite/libgomp.fortran/appendix-a/a.1= 6.1.f90:20 #1 0x00003fffb7b1f640 in gomp_thread_start () from /home/seurer/gcc/install/gcc-7.1.0/lib64/libgomp.so.1 #2 0x00003fffb7ad89d8 in start_thread (arg=3D0x3fff788af130) at pthread_create.c:314 #3 0x00003fffb7a2ef00 in clone () at ../sysdeps/unix/sysv/linux/powerpc/powerpc64/clone.S:104 >>From gcc-bugs-return-568302-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 10 20:37:08 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 100187 invoked by alias); 10 Jul 2017 20:37:06 -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 100081 invoked by uid 48); 10 Jul 2017 20:36:58 -0000 From: "glisse at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81346] Missed constant propagation into comparison Date: Mon, 10 Jul 2017 20:37:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: glisse at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jakub 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: 2017-07/txt/msg00853.txt.bz2 Content-length: 1002 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81346 --- Comment #6 from Marc Glisse --- (In reply to Jakub Jelinek from comment #5) > Untested WIP patch. Still no idea how to handle the build_range_check st= uff > at GIMPLE, that function is pretty huge. Shall I just always generate the > cast to utype and (acmp (minus (convert:utype @0) { lo; }) { himinuslo; }) > after doing the etype/utype computation and verification in (with {...}) = and > hope rest of match.pd optimizes that or add matchers for the various > optimizations in there? It seems reasonable to me to always emit something of the form (le (minus (convert:utype @0) cst) cst) here (or maybe even a bit_and of comparisons w= ith the extremities as an intermediate step), and add a separate (rather long) transformation that recognizes special cases of this pattern like (x-42u)<= =3D-43u (aka x>=3D42u). I am slightly concerned about unsafe things happening to pointers, but I probably shouldn't be. >>From gcc-bugs-return-568304-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 10 21:01:38 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 42313 invoked by alias); 10 Jul 2017 21:01: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 42168 invoked by uid 55); 10 Jul 2017 21:01:30 -0000 From: "msebor at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug other/81345] -Wall resets -Wstringop-overflow to 1 from the default 2 Date: Mon, 10 Jul 2017 21:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: other X-Bugzilla-Version: 7.0 X-Bugzilla-Keywords: diagnostic, patch X-Bugzilla-Severity: normal X-Bugzilla-Who: msebor at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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: 2017-07/txt/msg00855.txt.bz2 Content-length: 698 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81345 --- Comment #6 from Martin Sebor --- Author: msebor Date: Mon Jul 10 21:00:56 2017 New Revision: 250104 URL: https://gcc.gnu.org/viewcvs?rev=3D250104&root=3Dgcc&view=3Drev Log: PR other/81345 - -Wall resets -Wstringop-overflow to 1 from the default 2 gcc/c-family/ChangeLog: PR other/81345 * c.opt (-Wstringop-overflow): Set defaults in LangEnabledBy. gcc/testsuite/ChangeLog: PR other/81345 * gcc.dg/pr81345.c: New test. Added: trunk/gcc/testsuite/gcc.dg/pr81345.c Modified: trunk/gcc/c-family/ChangeLog trunk/gcc/c-family/c.opt trunk/gcc/testsuite/ChangeLog >>From gcc-bugs-return-568303-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 10 21:01:15 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 41287 invoked by alias); 10 Jul 2017 21:01: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 41193 invoked by uid 48); 10 Jul 2017 21:01:10 -0000 From: "msebor at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug other/81345] -Wall resets -Wstringop-overflow to 1 from the default 2 Date: Mon, 10 Jul 2017 21:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: other X-Bugzilla-Version: 7.0 X-Bugzilla-Keywords: diagnostic, patch X-Bugzilla-Severity: normal X-Bugzilla-Who: msebor at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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: 2017-07/txt/msg00854.txt.bz2 Content-length: 435 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81345 Martin Sebor changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Martin Sebor --- Fixed via r250104. >>From gcc-bugs-return-568305-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 10 21:02:02 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 43314 invoked by alias); 10 Jul 2017 21:02:01 -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 43204 invoked by uid 48); 10 Jul 2017 21:01:57 -0000 From: "jason at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/81073] [5/6/7/8 Regression] link failure as C++ misses to instanciate some objects Date: Mon, 10 Jul 2017 21:02:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.1.1 X-Bugzilla-Keywords: link-failure X-Bugzilla-Severity: normal X-Bugzilla-Who: jason at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jason at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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: 2017-07/txt/msg00856.txt.bz2 Content-length: 299 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81073 --- Comment #9 from Jason Merrill --- Created attachment 41711 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D41711&action=3Dedit patch to error on progmem with dynamic init Does this do what you had in mind? >>From gcc-bugs-return-568306-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 10 21:22:29 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 97347 invoked by alias); 10 Jul 2017 21:22:28 -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 96776 invoked by uid 55); 10 Jul 2017 21:22:23 -0000 From: "msebor at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/80397] missing -Wformat-overflow with arguments of enum types Date: Mon, 10 Jul 2017 21:22:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 7.0 X-Bugzilla-Keywords: diagnostic, missed-optimization, patch X-Bugzilla-Severity: normal X-Bugzilla-Who: msebor at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: 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: 2017-07/txt/msg00857.txt.bz2 Content-length: 829 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D80397 --- Comment #2 from Martin Sebor --- Author: msebor Date: Mon Jul 10 21:21:51 2017 New Revision: 250106 URL: https://gcc.gnu.org/viewcvs?rev=3D250106&root=3Dgcc&view=3Drev Log: PR tree-optimization/80397 - missing -Wformat-overflow with arguments of en= um types gcc/ChangeLog: PR tree-optimization/80397 * gimple-ssa-sprintf.c (format_integer): Use INTEGRAL_TYPE_P() instead of testing for equality to INTEGER_TYPE. gcc/testsuite/ChangeLog: PR tree-optimization/80397 * gcc.dg/tree-ssa/builtin-sprintf-warn-17.c: New test. Added: trunk/gcc/testsuite/gcc.dg/tree-ssa/builtin-sprintf-warn-19.c Modified: trunk/gcc/ChangeLog trunk/gcc/gimple-ssa-sprintf.c trunk/gcc/testsuite/ChangeLog >>From gcc-bugs-return-568307-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 10 21:23:37 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 99574 invoked by alias); 10 Jul 2017 21:23:37 -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 99543 invoked by uid 48); 10 Jul 2017 21:23:33 -0000 From: "msebor at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/80397] missing -Wformat-overflow with arguments of enum types Date: Mon, 10 Jul 2017 21:23:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 7.0 X-Bugzilla-Keywords: diagnostic, missed-optimization, patch X-Bugzilla-Severity: normal X-Bugzilla-Who: msebor at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cf_known_to_work 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: 2017-07/txt/msg00858.txt.bz2 Content-length: 430 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D80397 Martin Sebor changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |8.0 Known to fail| |7.1.0 --- Comment #3 from Martin Sebor --- Fixed via r250106. >>From gcc-bugs-return-568308-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 10 21:33:59 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 110238 invoked by alias); 10 Jul 2017 21:33: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 110136 invoked by uid 48); 10 Jul 2017 21:33:54 -0000 From: "grgoffe at yahoo dot com" To: gcc-bugs@gcc.gnu.org Subject: =?UTF-8?B?W0J1ZyBzYW5pdGl6ZXIvODEwNjZdIHNhbml0aXplcl9zdG9wdGhld29ybGRf?= =?UTF-8?B?bGludXhfbGliY2RlcC5jYzoyNzY6MjI6IGVycm9yOiBhZ2dyZWdhdGUg4oCY?= =?UTF-8?B?c2lnYWx0c3RhY2sgaGFuZGxlcl9zdGFja+KAmSBoYXMgaW5jb21wbGV0ZSB0?= =?UTF-8?B?eXBlIGFuZCBjYW5ub3QgYmUgZGVmaW5lZA==?= Date: Mon, 10 Jul 2017 21:33:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: normal X-Bugzilla-Who: grgoffe at yahoo dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: 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: 2017-07/txt/msg00859.txt.bz2 Content-length: 2683 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81066 George R. Goffe changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |grgoffe at yahoo dot com --- Comment #9 from George R. Goffe --- Hi, I'm building the "latest" gcc on a Fedora 27 (rawhide) system and am seeing this same problem. x86_64-pc-linux-gnu/libsanitizer/tsan# /tools/gcc/obj-x86_64-pc-linux-gnu/./gcc/xgcc --save-temps -shared-libgcc -B/tools/gcc/obj-x86_64-pc-linux-gnu/./gcc -nostdinc++ -L/tools/gcc/obj-x86_64-pc-linux-gnu/x86_64-pc-linux-gnu/libstdc++-v3/src -L/tools/gcc/obj-x86_64-pc-linux-gnu/x86_64-pc-linux-gnu/libstdc++-v3/src/.= libs -L/tools/gcc/obj-x86_64-pc-linux-gnu/x86_64-pc-linux-gnu/libstdc++-v3/libsu= pc++/.libs -B/usr/lsd/Linux/x86_64-pc-linux-gnu/bin/ -B/usr/lsd/Linux/x86_64-pc-linux-gnu/lib/ -isystem /usr/lsd/Linux/x86_64-pc-linux-gnu/include -isystem /usr/lsd/Linux/x86_64-pc-linux-gnu/sys-include -D_GNU_SOURCE -D_DEBUG -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -DCAN_SANITIZE_UB=3D0 -I. -I../../../../gcc/libsanitizer/tsan -I.. -I ../../../../gcc/libsanitizer -I ../../../../gcc/libsanitizer/include -Wall = -W -Wno-unused-parameter -Wwrite-strings -pedantic -Wno-long-long -fPIC -fno-builtin -fno-exceptions -fno-rtti -fomit-frame-pointer -funwind-tables -fvisibility=3Dhidden -Wno-variadic-macros -I../../libstdc++-v3/include -I../../libstdc++-v3/include/x86_64-pc-linux-gnu -I../../../../gcc/libsanitizer/../libstdc++-v3/libsupc++ -std=3Dgnu++11 -g = -O2 -D_GNU_SOURCE -MT tsan_platform_linux.lo -MD -MP -MF .deps/tsan_platform_linux.Tpo -c ../../../../gcc/libsanitizer/tsan/tsan_platform_linux.cc -fPIC -DPIC -o .libs/tsan_platform_linux.o ../../../../gcc/libsanitizer/tsan/tsan_platform_linux.cc: In function =E2= =80=98int __tsan::ExtractResolvFDs(void*, int*, int)=E2=80=99: ../../../../gcc/libsanitizer/tsan/tsan_platform_linux.cc:290:16: error: =E2= =80=98statp=E2=80=99 was not declared in this scope __res_state *statp =3D (__res_state*)state; ^~~~~ ../../../../gcc/libsanitizer/tsan/tsan_platform_linux.cc:290:16: note: suggested alternative: =E2=80=98state=E2=80=99 __res_state *statp =3D (__res_state*)state; ^~~~~ state ../../../../gcc/libsanitizer/tsan/tsan_platform_linux.cc:290:37: error: expected primary-expression before =E2=80=98)=E2=80=99 token __res_state *statp =3D (__res_state*)state; ^ glibc-2.25.90-21.fc27.x86_64 gcc-7.1.1-2.fc27.x86_64 >>From gcc-bugs-return-568309-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 10 21:36:12 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 24232 invoked by alias); 10 Jul 2017 21:36: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 24182 invoked by uid 48); 10 Jul 2017 21:36:05 -0000 From: "tetra2005 at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/41992] ICE on invalid dereferencing of void * Date: Mon, 10 Jul 2017 21:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 4.4.1 X-Bugzilla-Keywords: ice-on-invalid-code X-Bugzilla-Severity: minor X-Bugzilla-Who: tetra2005 at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: 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: 2017-07/txt/msg00860.txt.bz2 Content-length: 440 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D41992 Yuri Gribov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tetra2005 at gmail dot com --- Comment #4 from Yuri Gribov --- Fixed long ago, most probly in r172298. Could someone close? >>From gcc-bugs-return-568310-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 10 22:01:44 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 63467 invoked by alias); 10 Jul 2017 22:01: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 63409 invoked by uid 55); 10 Jul 2017 22:01:39 -0000 From: "uros at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/81375] [6/7/8 Regression] unrecognizable insn Date: Mon, 10 Jul 2017 22:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 7.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: uros at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: ubizjak at gmail dot com X-Bugzilla-Target-Milestone: 6.5 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: 2017-07/txt/msg00861.txt.bz2 Content-length: 772 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81375 --- Comment #2 from uros at gcc dot gnu.org --- Author: uros Date: Mon Jul 10 22:01:06 2017 New Revision: 250107 URL: https://gcc.gnu.org/viewcvs?rev=3D250107&root=3Dgcc&view=3Drev Log: PR target/81375 * config/i386/i386.md (divsf3): Add TARGET_SSE to TARGET_SSE_MATH. (rcpps): Ditto. (*rsqrtsf2_sse): Ditto. (rsqrtsf2): Ditto. (div3): Macroize insn from divdf3 and divsf3 using MODEF mode iterator. testsuite/ChangeLog: PR target/81375 * gcc.target/i386/pr81375.c: New test. Added: trunk/gcc/testsuite/gcc.target/i386/pr81375.c Modified: trunk/gcc/ChangeLog trunk/gcc/config/i386/i386.md trunk/gcc/testsuite/ChangeLog >>From gcc-bugs-return-568311-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 10 22:21:27 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 68965 invoked by alias); 10 Jul 2017 22:21: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 68892 invoked by uid 48); 10 Jul 2017 22:21:21 -0000 From: "segher at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/81288] [5/6/7/8 Regression] ICE on 32-bit BE powerpc targets -w -misel -O2 (-O3, -Ofast, -Os) Date: Mon, 10 Jul 2017 22:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rtl-optimization X-Bugzilla-Version: unknown X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: segher at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.5 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: 2017-07/txt/msg00862.txt.bz2 Content-length: 1177 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81288 Segher Boessenkool changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-07-10 Ever confirmed|0 |1 --- Comment #1 from Segher Boessenkool --- It doesn't fail for me, -misel, either -m32 or -m64, either -O2, -Os, -O3, not with trunk and also not with four weeks ago. Ah. With -mcpu=3D8548 it segfaults. It is some unbounded recursion: #62 0x000000001118bd14 in fold_rtx (x=3D0x3fffb6bf2130, insn=3Dinsn@entry= =3D0x0) at /home/segher/src/gcc/gcc/cse.c:3411 Joy, corrupted stack. "x" seems to be some isel (no surprise really), probably this one (because it's the only isel in the whole program): (insn 22 21 23 5 (set (reg:SI 137) (if_then_else:SI (eq (reg:CC 138) (const_int 0 [0])) (const_int 0 [0]) (reg:SI 139))) "81288.c":8 330 {isel_signed_si} (nil)) Anyway, confirmed. >>From gcc-bugs-return-568312-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 10 22:44:21 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 38580 invoked by alias); 10 Jul 2017 22:44:21 -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 29925 invoked by uid 48); 10 Jul 2017 22:44:13 -0000 From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: =?UTF-8?B?W0J1ZyBzYW5pdGl6ZXIvODEwNjZdIHNhbml0aXplcl9zdG9wdGhld29ybGRf?= =?UTF-8?B?bGludXhfbGliY2RlcC5jYzoyNzY6MjI6IGVycm9yOiBhZ2dyZWdhdGUg4oCY?= =?UTF-8?B?c2lnYWx0c3RhY2sgaGFuZGxlcl9zdGFja+KAmSBoYXMgaW5jb21wbGV0ZSB0?= =?UTF-8?B?eXBlIGFuZCBjYW5ub3QgYmUgZGVmaW5lZA==?= Date: Mon, 10 Jul 2017 22:44:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: 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: 2017-07/txt/msg00863.txt.bz2 Content-length: 352 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81066 --- Comment #10 from Jakub Jelinek --- I think the tsan build issue can be fixed just by replacing __res_state *statp =3D (__res_state*)state; line with struct __res_state *statp =3D (struct __res_state*)state; It should then build hopefully with both old and new glibc. >>From gcc-bugs-return-568313-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 10 23:36:26 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 12352 invoked by alias); 10 Jul 2017 23:36: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 12265 invoked by uid 48); 10 Jul 2017 23:36:21 -0000 From: "grgoffe at yahoo dot com" To: gcc-bugs@gcc.gnu.org Subject: =?UTF-8?B?W0J1ZyBzYW5pdGl6ZXIvODEwNjZdIHNhbml0aXplcl9zdG9wdGhld29ybGRf?= =?UTF-8?B?bGludXhfbGliY2RlcC5jYzoyNzY6MjI6IGVycm9yOiBhZ2dyZWdhdGUg4oCY?= =?UTF-8?B?c2lnYWx0c3RhY2sgaGFuZGxlcl9zdGFja+KAmSBoYXMgaW5jb21wbGV0ZSB0?= =?UTF-8?B?eXBlIGFuZCBjYW5ub3QgYmUgZGVmaW5lZA==?= Date: Mon, 10 Jul 2017 23:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: normal X-Bugzilla-Who: grgoffe at yahoo dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: 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: 2017-07/txt/msg00864.txt.bz2 Content-length: 201 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81066 --- Comment #11 from George R. Goffe --- Jakub, I just tried your suggestion... It worked on "my" platform! George... >>From gcc-bugs-return-568314-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 00:41:14 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 125525 invoked by alias); 11 Jul 2017 00:41: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 125453 invoked by uid 48); 11 Jul 2017 00:41:09 -0000 From: "babokin at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/81332] GCC crash during "RTL pass: expand" - verify_flow_info: REG_BR_PROB does not match cfg Date: Tue, 11 Jul 2017 00:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rtl-optimization X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: babokin 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: 2017-07/txt/msg00865.txt.bz2 Content-length: 245 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81332 --- Comment #1 from Dmitry Babokin --- I've jut hit another instance on this bug, which mean that it's probably not too rare and quite possible to hit in the wild. >>From gcc-bugs-return-568315-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 02:22:08 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 32250 invoked by alias); 11 Jul 2017 02:22:08 -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 27908 invoked by uid 48); 11 Jul 2017 02:22:02 -0000 From: "babokin at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/81387] New: UBSAN consumes too much memory at -O2 Date: Tue, 11 Jul 2017 02:22:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: babokin at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone 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: 2017-07/txt/msg00866.txt.bz2 Content-length: 3631 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81387 Bug ID: 81387 Summary: UBSAN consumes too much memory at -O2 Product: gcc Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxi= n at gcc dot gnu.org Target Milestone: --- Created attachment 41712 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D41712&action=3Dedit reproducer I understand that compiling with UBSAN should require more memory, but in c= ase of scalar code increase in memory consumption by 50x looks a bit too much. -O0: 13sec, 0.8Gb -O2: 5s, 0.4Gb -O0 -fsanitize=3Dundefined: 100s, 2.7Gb -O2 -fsanitize=3Dundefined: 255s 42.9Gb So, it may be useful test case to make sure that memory consumption is reasonable and not beyond expected limits. Here is stack when memory consumption goes wild: #0 bitmap_elt_insert_after(bitmap_head*, bitmap_element*, unsigned int) ()= at ../../gcc/gcc/bitmap.c:409 #1 0x0000000000a6d7cd in bitmap_set_range (head=3Dhead@entry=3D0x249bac630, start=3Dstart@entry=3D0, count=3D) at ../../gcc/gcc/bitmap.c= :1233 #2 0x0000000000a6fd3e in bitmap_set_range (head=3Dhead@entry=3D0x249bac630, start=3Dstart@entry=3D0, count=3D) at ../../gcc/gcc/bitmap.c= :1197 #3 0x0000000000b0b186 in df_mir_alloc(bitmap_head*) () at ../../gcc/gcc/df-problems.c:1913 #4 0x0000000000b05971 in df_analyze_problem (dflow=3D0xe5f0440, blocks_to_consider=3D0x5232ed8, postorder=3D0x27ebe678, n_blocks=3D120403) = at ../../gcc/gcc/df-core.c:1161 #5 0x0000000000b05a7c in df_analyze_1() () at ../../gcc/gcc/df-core.c:1222 #6 0x00000000015d8cbf in find_and_remove_re () at ../../gcc/gcc/ree.c:1216 #7 rest_of_handle_ree () at ../../gcc/gcc/ree.c:1310 #8 (anonymous namespace)::pass_ree::execute(function*) () at ../../gcc/gcc/ree.c:1338 #9 0x0000000000dce3bb in execute_one_pass(opt_pass*) () at ../../gcc/gcc/passes.c:2492 #10 0x0000000000dcec15 in execute_pass_list_1(opt_pass*) () at ../../gcc/gcc/passes.c:2581 #11 0x0000000000dcec27 in execute_pass_list_1(opt_pass*) () at ../../gcc/gcc/passes.c:2582 #12 0x0000000000dcec27 in execute_pass_list_1(opt_pass*) () at ../../gcc/gcc/passes.c:2582 #13 0x0000000000dcec59 in execute_pass_list(function*, opt_pass*) () at ../../gcc/gcc/passes.c:2592 #14 0x0000000000ae11e0 in cgraph_node::expand() () at ../../gcc/gcc/cgraphunit.c:2052 #15 0x0000000000ae2361 in expand_all_functions () at ../../gcc/gcc/cgraphunit.c:2188 #16 symbol_table::compile() [clone .part.54] () at ../../gcc/gcc/cgraphunit.c:2540 #17 0x0000000000ae4807 in compile (this=3D0x7fb63a52e100) at ../../gcc/gcc/cgraphunit.c:2632 #18 symbol_table::finalize_compilation_unit (this=3D0x7fb63a52e100) at ../../gcc/gcc/cgraphunit.c:2629 #19 0x0000000000e9c018 in compile_file () at ../../gcc/gcc/toplev.c:493 #20 0x00000000007ffcb6 in do_compile () at ../../gcc/gcc/toplev.c:2021 #21 toplev::main(int, char**) () at ../../gcc/gcc/toplev.c:2155 #22 0x0000000000801cbb in main (argc=3D15, argv=3D0x7ffe16a14d48) at ../../gcc/gcc/main.c:39 I don't mind if this bug is closed as "will not be fixed", but such behavio= ur is definitely make using UBSAN problematic on larger code bases, as it may basically nuke the build system. And I'm not sure if it's UBSAN implementat= ion is to blame or DF analysis consumes more than it should. >>From gcc-bugs-return-568316-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 02:55:45 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 123577 invoked by alias); 11 Jul 2017 02:55: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 123532 invoked by uid 48); 11 Jul 2017 02:55:40 -0000 From: "terrelln at fb dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81388] New: Incorrect code generation with -O1 -fno-strict-overflow Date: Tue, 11 Jul 2017 02:55: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: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: terrelln at fb 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: 2017-07/txt/msg00867.txt.bz2 Content-length: 1046 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81388 Bug ID: 81388 Summary: Incorrect code generation with -O1 -fno-strict-overflow Product: gcc Version: 7.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: terrelln at fb dot com Target Milestone: --- gcc 7.1 on x86 produces incorrect output for correct code. gcc 6.3 produced correct assembly. See https://godbolt.org/g/mLyxGz or below for the code and generated assembly. code: .---- // -O1 -fno-strict-overflow void bar(); void foo(char *dst) { char *const end =3D dst; do { bar(); dst +=3D 2; } while (dst < end); } `---- assembly: .---- foo(char*): push rbx movabs rbx, -9223372036854775808 .L2: call bar() sub rbx, 1 jne .L2 pop rbx ret `---- >>From gcc-bugs-return-568317-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 03:07:52 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 50444 invoked by alias); 11 Jul 2017 03:07:52 -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 50396 invoked by uid 48); 11 Jul 2017 03:07:47 -0000 From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81388] Incorrect code generation with -O1 -fno-strict-overflow Date: Tue, 11 Jul 2017 03:07:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 7.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: 2017-07/txt/msg00868.txt.bz2 Content-length: 657 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81388 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Andrew Pinski --- -fno-strict-overflow Does not effect Pointers. Pointers overflow is separate from integer signed overflow and it is always undefined if the pointer overflow. That is once a pointer is non-null, add= ing to it can never reach be null. >>From gcc-bugs-return-568318-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 03:13:18 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 63498 invoked by alias); 11 Jul 2017 03:13: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 63445 invoked by uid 48); 11 Jul 2017 03:13:12 -0000 From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81388] Incorrect code generation with -O1 -fno-strict-overflow Date: Tue, 11 Jul 2017 03:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: 2017-07/txt/msg00869.txt.bz2 Content-length: 650 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81388 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|INVALID |--- --- Comment #2 from Andrew Pinski --- void bar(); void foo(char *dst) { char *const end =3D dst; do { bar(); dst +=3D 2; } while (dst < end); } Hmm actually I am backwards here. end + 2 < end is always false. >>From gcc-bugs-return-568319-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 03:39:32 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 108038 invoked by alias); 11 Jul 2017 03:39: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 107763 invoked by uid 48); 11 Jul 2017 03:39:25 -0000 From: "msebor at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/79459] Please add enable_if and diagnose_if attributes (from clang) Date: Tue, 11 Jul 2017 03:39:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: unknown X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: enhancement X-Bugzilla-Who: msebor at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc 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: 2017-07/txt/msg00870.txt.bz2 Content-length: 1567 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D79459 Martin Sebor changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |diagnostic Status|UNCONFIRMED |NEW Last reconfirmed| |2017-07-11 CC| |msebor at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from Martin Sebor --- Confirmed. I think a feature along these lines could be useful as a generalization of some existing warnings (such as -Walloc-zero, -Walloc-size-larger-than, or -Wnonnull) and future ones like those. An aspect of the attribute that might be worth handling differently in GCC = than in Clang is whether the checking should be restricted to just arguments that are constant expressions or also applied to arguments that are the result of constant or value range propagation (or perhaps even other forms of optimization. I think the latter would make it more powerful in GCC, but I wonder if there might also be cases where it could lead to excessive false positives. If there were such cases, generalizing the attribute to specify what kinds of expressions the diagnostic should consider might be worthwhile (i.e., constant expressions only, or even those where the expression is kno= wn to have a value or be in some range as a result of various optimizations). >>From gcc-bugs-return-568320-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 04:14:47 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 81053 invoked by alias); 11 Jul 2017 04:14: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 80922 invoked by uid 48); 11 Jul 2017 04:14:43 -0000 From: "rockeet at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/81389] New: _mm_cmpestri segfault on -O0 Date: Tue, 11 Jul 2017 04:14:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rockeet 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: 2017-07/txt/msg00871.txt.bz2 Content-length: 869 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81389 Bug ID: 81389 Summary: _mm_cmpestri segfault on -O0 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: rockeet at gmail dot com Target Milestone: --- With option -O0, intrinsic _mm_cmpestri generate a mmload and a _mm_cmpestr= i, in which mmload raise a CPU hardware exception. The reason is: mmload require memory align to 16, but _mm_cmpestri directly= on memory does not require memory align. It is OK with option -O3, because the compiler does not generate mmload, it generate an mm_cmpestri directly on memory. I had noticed this bug in gcc-4.7, serveral years later, the bug is still there(gcc-6.3)... >>From gcc-bugs-return-568321-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 04:48:54 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 35864 invoked by alias); 11 Jul 2017 04:48:53 -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 35740 invoked by uid 48); 11 Jul 2017 04:48:46 -0000 From: "asolokha at gmx dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/81332] GCC crash during "RTL pass: expand" - verify_flow_info: REG_BR_PROB does not match cfg Date: Tue, 11 Jul 2017 04:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rtl-optimization X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: asolokha at gmx dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: 2017-07/txt/msg00872.txt.bz2 Content-length: 415 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81332 Arseny Solokha changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |asolokha at gmx dot com --- Comment #2 from Arseny Solokha --- It well may be a duplicate of PR81030. >>From gcc-bugs-return-568322-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 05:34:05 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 93021 invoked by alias); 11 Jul 2017 05:34:05 -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 92961 invoked by uid 55); 11 Jul 2017 05:34:00 -0000 From: "uros at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/81375] [6/7/8 Regression] unrecognizable insn Date: Tue, 11 Jul 2017 05:34:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 7.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: uros at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: ubizjak at gmail dot com X-Bugzilla-Target-Milestone: 6.5 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: 2017-07/txt/msg00873.txt.bz2 Content-length: 836 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81375 --- Comment #3 from uros at gcc dot gnu.org --- Author: uros Date: Tue Jul 11 05:32:39 2017 New Revision: 250113 URL: https://gcc.gnu.org/viewcvs?rev=3D250113&root=3Dgcc&view=3Drev Log: PR target/81375 * config/i386/i386.md (divsf3): Add TARGET_SSE to TARGET_SSE_MATH. (rcpps): Ditto. (*rsqrtsf2_sse): Ditto. (rsqrtsf2): Ditto. (div3): Macroize insn from divdf3 and divsf3 using MODEF mode iterator. testsuite/ChangeLog: PR target/81375 * gcc.target/i386/pr81375.c: New test. Added: branches/gcc-7-branch/gcc/testsuite/gcc.target/i386/pr81375.c Modified: branches/gcc-7-branch/gcc/ChangeLog branches/gcc-7-branch/gcc/config/i386/i386.md branches/gcc-7-branch/gcc/testsuite/ChangeLog >>From gcc-bugs-return-568323-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 06:31:03 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 113048 invoked by alias); 11 Jul 2017 06:31: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 111637 invoked by uid 48); 11 Jul 2017 06:30:58 -0000 From: "glisse at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81388] Incorrect code generation with -O1 -fno-strict-overflow Date: Tue, 11 Jul 2017 06:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: glisse at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: 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: 2017-07/txt/msg00874.txt.bz2 Content-length: 339 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81388 --- Comment #3 from Marc Glisse --- (it helps to describe in what way the code is wrong, for instance in a way = that makes the testcase abort) Apparently ivcanon thinks the number of iterations is constant, as it would= be for the condition dst !=3D end. >>From gcc-bugs-return-568324-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 06:40:05 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 19473 invoked by alias); 11 Jul 2017 06:40:04 -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 19385 invoked by uid 48); 11 Jul 2017 06:40:00 -0000 From: "terrelln at fb dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81388] Incorrect code generation with -O1 -fno-strict-overflow Date: Tue, 11 Jul 2017 06:40:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: terrelln at fb 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: 2017-07/txt/msg00875.txt.bz2 Content-length: 350 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81388 --- Comment #4 from Nick Terrell --- Good point Marc. The generated assembly is wrong because the loop should be run once, but it= is run 2^63 times. Changing the amount dst is incremented by to 4 makes it run 2^62 times, and changing it to 8 makes it run 2^61 times. >>From gcc-bugs-return-568326-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 07:21:29 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 79239 invoked by alias); 11 Jul 2017 07:21:29 -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 78736 invoked by uid 55); 11 Jul 2017 07:21:22 -0000 From: "vries at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/79939] [nvptx] gcc hangs in nvptx_assemble_value Date: Tue, 11 Jul 2017 07:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 7.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: vries 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: 2017-07/txt/msg00877.txt.bz2 Content-length: 768 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D79939 --- Comment #4 from Tom de Vries --- Author: vries Date: Tue Jul 11 07:20:47 2017 New Revision: 250119 URL: https://gcc.gnu.org/viewcvs?rev=3D250119&root=3Dgcc&view=3Drev Log: Backport "Disable constant pool for nvptx" 2017-07-11 Tom de Vries backport from mainline: 2017-06-11 Tom de Vries PR target/79939 * config/nvptx/nvptx.c (nvptx_cannot_force_const_mem): New function. Return true. (TARGET_CANNOT_FORCE_CONST_MEM): Redefine to nvptx_cannot_force_const_mem. Modified: branches/gomp-4_0-branch/gcc/ChangeLog.gomp branches/gomp-4_0-branch/gcc/config/nvptx/nvptx.c >>From gcc-bugs-return-568325-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 07:21:14 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 78067 invoked by alias); 11 Jul 2017 07:21: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 77776 invoked by uid 55); 11 Jul 2017 07:21:09 -0000 From: "vries at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/80855] [nvptx] missing sorry("target cannot support label values" Date: Tue, 11 Jul 2017 07:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: 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: 2017-07/txt/msg00876.txt.bz2 Content-length: 954 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D80855 --- Comment #4 from Tom de Vries --- Author: vries Date: Tue Jul 11 07:20:34 2017 New Revision: 250118 URL: https://gcc.gnu.org/viewcvs?rev=3D250118&root=3Dgcc&view=3Drev Log: Backport: Add "sorry, target cannot support label values" for nvptx 2017-07-11 Tom de Vries backport from mainline: 2017-06-09 Tom de Vries PR target/80855 * config/nvptx/nvptx.md (define_expand "mov"): Error out with "target cannot support label values" when encountering LABEL_REF. * gcc.target/nvptx/label-values.c: New test. Added: branches/gomp-4_0-branch/gcc/testsuite/gcc.target/nvptx/label-values.c Modified: branches/gomp-4_0-branch/gcc/ChangeLog.gomp branches/gomp-4_0-branch/gcc/config/nvptx/nvptx.md branches/gomp-4_0-branch/gcc/testsuite/ChangeLog.gomp >>From gcc-bugs-return-568327-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 07:53:33 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 18833 invoked by alias); 11 Jul 2017 07:53: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 62691 invoked by uid 48); 11 Jul 2017 07:52:42 -0000 From: "segher at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/81317] builtin_vec_ld fails for powerpc with altivec Date: Tue, 11 Jul 2017 07:53:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: segher at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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: 2017-07/txt/msg00878.txt.bz2 Content-length: 1324 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81317 Segher Boessenkool changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-07-11 CC| |segher at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #8 from Segher Boessenkool --- Hi Randy, It is development stage 1, which means we are all pretty busy, so that's why no one had looked at your bug yet. I cannot get the "smaller reproducer" to fail (with trunk); but your minimal testcase in comment 1 fails alright (needs no compiler options at all): 81317-2.c:4:21: internal compiler error: Segmentation fault ( 1, jsimd_ycc_extbgrx_convert_altivec_outptr ) ^ 0x102e1ad4 tree_class_check(tree_node*, tree_code_class, char const*, int, = char=20 const*) /home/segher/src/gcc/gcc/tree.h:3205 0x102e1ad4 altivec_resolve_overloaded_builtin(unsigned int, tree_node*, voi= d*) /home/segher/src/gcc/gcc/config/rs6000/rs6000-c.c:6458 (The first arg to tree_class_check is NULL). So, confirmed. >>From gcc-bugs-return-568328-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 07:55:49 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 48802 invoked by alias); 11 Jul 2017 07:55:49 -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 95550 invoked by uid 48); 11 Jul 2017 07:54:55 -0000 From: "rdapp at linux dot vnet.ibm.com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/81362] [8.0 regression] FAIL: gcc.dg/vect/no-vfa-vect-57.c execution test Date: Tue, 11 Jul 2017 07:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: rdapp at linux dot vnet.ibm.com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: 2017-07/txt/msg00879.txt.bz2 Content-length: 2097 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81362 --- Comment #5 from rdapp at linux dot vnet.ibm.com --- Ah, npeel is set by vect_peeling_hash_get_lowest_cost although the corresponding dr is not used afterwards. It should be save to get rid of t= he npeel parameter since we use the returned peeling's npeel anyway. I think = the same is true for=20 body_cost_vec but it's not used afterwards so doesn't cause problems. The following fixes the regression for me: index 5103ba1..257be41 100644=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 [0/92965] --- a/gcc/tree-vect-data-refs.c +++ b/gcc/tree-vect-data-refs.c @@ -1347,7 +1347,6 @@ vect_peeling_hash_get_lowest_cost (_vect_peel_info **slot, static struct _vect_peel_extended_info vect_peeling_hash_choose_best_peeling (hash_table *peeling_htab, loop_vec_info loop_vinfo, - unsigned int *npeel, stmt_vector_for_cost *body_cost_vec) { struct _vect_peel_extended_info res; @@ -1371,7 +1370,6 @@ vect_peeling_hash_choose_best_peeling (hash_table *pee ling_hta res.outside_cost =3D 0; } - *npeel =3D res.peel_info.npeel; *body_cost_vec =3D res.body_cost_vec; return res; } @@ -1812,7 +1810,7 @@ vect_enhance_data_refs_alignment (loop_vec_info loop_vinfo) unless aligned. So we try to choose the best possible peeling fr= om the hash table. */ peel_for_known_alignment =3D vect_peeling_hash_choose_best_peeling - (&peeling_htab, loop_vinfo, &npeel, &body_cost_vec); + (&peeling_htab, loop_vinfo, &body_cost_vec); } /* Compare costs of peeling for known and unknown alignment. */ >>From gcc-bugs-return-568329-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 08:33:21 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 45638 invoked by alias); 11 Jul 2017 08:33:21 -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 45526 invoked by uid 48); 11 Jul 2017 08:33:17 -0000 From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/81387] UBSAN consumes too much memory at -O2 Date: Tue, 11 Jul 2017 08:33:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: 2017-07/txt/msg00880.txt.bz2 Content-length: 632 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81387 --- Comment #1 from Jakub Jelinek --- I'm afraid it is unfixable, if you want smaller memory consumption, you eit= her need smaller routines, or use -fno-sanitize-recover=3Dall, or do multiple b= uilds with selected subsets of -fsanitize=3Dundefined, so that you don't have tha= t many checks in one function, or use -O1 on the larger functions to avoid many optimizations that are e.g. quadratic in the number of basic blocks. The UBSAN checks are many and especially if they are recoverable, they incr= ease the number of basic blocks way too much. >>From gcc-bugs-return-568331-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 08:43:57 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 111627 invoked by alias); 11 Jul 2017 08:43: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 111124 invoked by uid 48); 11 Jul 2017 08:43:50 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/81381] std::basic_stringbuf only works with DefaultConstructible allocators Date: Tue, 11 Jul 2017 08:43:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: rejects-valid X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: redi at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.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: 2017-07/txt/msg00882.txt.bz2 Content-length: 291 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81381 Jonathan Wakely changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |8.0 >>From gcc-bugs-return-568330-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 08:43:48 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 110735 invoked by alias); 11 Jul 2017 08:43: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 110648 invoked by uid 48); 11 Jul 2017 08:43:43 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/81381] std::basic_stringbuf only works with DefaultConstructible allocators Date: Tue, 11 Jul 2017 08:43:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: rejects-valid X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: redi at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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: 2017-07/txt/msg00881.txt.bz2 Content-length: 465 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81381 Jonathan Wakely changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Jonathan Wakely --- Not important to backport, so fixed for GCC 8. >>From gcc-bugs-return-568332-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 09:24:54 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 557 invoked by alias); 11 Jul 2017 09:24:53 -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 128808 invoked by uid 48); 11 Jul 2017 09:24:41 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/59521] __builtin_expect not effective in switch Date: Tue, 11 Jul 2017 09:24:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: 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: 2017-07/txt/msg00883.txt.bz2 Content-length: 1085 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D59521 --- Comment #5 from Martin Li=C5=A1ka --- Ok, your patch is definitely needed to properly propagate the builtin probability to a proper edge. Apart from that I added code that preserves t= hat probability incombine_predictions_for_bb. Having that we're quite close: $ ./xgcc -B. ~/Programming/testcases/pr59521.c -O2 -c -S -fdump-tree-optimized=3D/dev/stdout ;; Function f (f, funcdef_no=3D11, decl_uid=3D2306, cgraph_uid=3D11, symbol= _order=3D11) Removing basic block 7 f (int ch) { [100.00%] [count: INV]: switch (ch_4(D)) [3.33%] [count: INV], case 3: [3.33%] [count: INV], case 42: [3.33%] [count: INV], case 333: [90.00%] [count: INV]> But still there's a missing piece that will rearrange switch statement so t= hat case 333 will be first: f: .LFB11: .cfi_startproc cmpl $42, %edi je .L3 cmpl $333, %edi jne .L8 movl $.LC2, %edi jmp puts Can you please Yuri take a look? >>From gcc-bugs-return-568333-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 09:25:56 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 21044 invoked by alias); 11 Jul 2017 09:25: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 20161 invoked by uid 48); 11 Jul 2017 09:25:51 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/59521] __builtin_expect not effective in switch Date: Tue, 11 Jul 2017 09:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: 2017-07/txt/msg00884.txt.bz2 Content-length: 243 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D59521 --- Comment #6 from Martin Li=C5=A1ka --- Created attachment 41713 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D41713&action=3Dedit Semi-working patch >>From gcc-bugs-return-568334-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 09:26:59 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 22521 invoked by alias); 11 Jul 2017 09:26: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 22465 invoked by uid 48); 11 Jul 2017 09:26:54 -0000 From: "mpolacek at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/81364] Bogus -Wmultistatement-macros warning Date: Tue, 11 Jul 2017 09:26:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: preprocessor X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mpolacek at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc 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: 2017-07/txt/msg00885.txt.bz2 Content-length: 461 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81364 Marek Polacek changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |mpolacek at gcc dot gnu.org Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot= gnu.org >>From gcc-bugs-return-568335-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 09:29:27 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 73530 invoked by alias); 11 Jul 2017 09:29: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 73459 invoked by uid 48); 11 Jul 2017 09:29:22 -0000 From: "bugzilla@poradnik-webmastera.com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/81391] New: Use of parenthesis disables warning about incorrect size parameter Date: Tue, 11 Jul 2017 09:29: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: 5.4.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: bugzilla@poradnik-webmastera.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: 2017-07/txt/msg00886.txt.bz2 Content-length: 1411 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81391 Bug ID: 81391 Summary: Use of parenthesis disables warning about incorrect size parameter Product: gcc Version: 5.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: bugzilla@poradnik-webmastera.com Target Milestone: --- When code below is compiled, gcc complains only about first call to strncpy. 2nd call has the same problem as the 1st one (sizeof pointer used as buffer size), but there is no warning about it - parenthesis added around sizeof() silenced this warning. It is recommended to use additional parenthesis arou= nd params in macrofunctions, so some bugs there may went unnoticed. Tested with gcc 4.8.5 (Linux) and gcc 5.4.0 (Cygwin). #include int main() { char buf[10], *ptr =3D buf; strncpy(ptr, "a", sizeof(ptr)); strncpy(ptr, "a", (sizeof(ptr))); return 0; } $ gcc -o test test.c -Wall -O2 test.c: In function =E2=80=98main=E2=80=99: test.c:6:29: warning: argument to =E2=80=98sizeof=E2=80=99 in =E2=80=98strn= cpy=E2=80=99 call is the same expression as the destination; did you mean to provide an explicit length? [-Wsizeof-pointer-memaccess] strncpy(ptr, "a", sizeof(ptr)); ^ >>From gcc-bugs-return-568336-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 09:34:21 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 102810 invoked by alias); 11 Jul 2017 09:34:21 -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 102721 invoked by uid 48); 11 Jul 2017 09:34:17 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/81387] UBSAN consumes too much memory at -O2 Date: Tue, 11 Jul 2017 09:34:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: 2017-07/txt/msg00887.txt.bz2 Content-length: 270 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81387 --- Comment #2 from Martin Li=C5=A1ka --- Just for curiosity, I tried to use clang++ 4.0.0 and clang++ pr81387.ii -c = -O2 -fsanitize=3Dundefined took me about 180s and memory was ~2.5GB. >>From gcc-bugs-return-568337-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 09:37:15 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 48889 invoked by alias); 11 Jul 2017 09:37: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 48841 invoked by uid 48); 11 Jul 2017 09:37:11 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/45708] fstream reads after writes, or vice versa, don't work Date: Tue, 11 Jul 2017 09:37:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 4.5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WONTFIX X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: 2017-07/txt/msg00888.txt.bz2 Content-length: 1423 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D45708 --- Comment #4 from Jonathan Wakely --- (In reply to David Krauss from comment #0) > basic_filebuf (and therefore fstream) does not allow you to put a write > operation directly after a read operation, or vice versa. Instead, the wr= ite > and the read must be separated by a seek or tell (tell being equivalent t= o a > seek-to-current-position). >=20 > As the Standard specifies behavior in terms of the file's contents, the > current position in the file, and get and put areas, this requirement has= no > basis in it. I disagree, and would have closed this as INVALID not WONTFIX. C++14 27.9 [filebuf]: The restrictions on reading and writing a sequence controlled by an object = of class basic_filebuf are the same as for reading and writing = with the C standard library FILEs. C11 7.21.5.3: When a file is opened with update mode ('+' as the second or third characte= r in the above list of mode argument values), both input and output may be perfo= rmed on the associated stream. However, output shall not be directly followed by input without an intervening call to the fflush function or to a file positioning function (fseek, fsetpos, or rewind), and input shall not be directly followed by output without an intervening call to a file positioni= ng function, unless the input operation encounters end-of-file. >>From gcc-bugs-return-568338-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 09:38:17 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 50681 invoked by alias); 11 Jul 2017 09:38: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 50557 invoked by uid 48); 11 Jul 2017 09:38:10 -0000 From: "tetra2005 at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/59521] __builtin_expect not effective in switch Date: Tue, 11 Jul 2017 09:38:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: tetra2005 at gmail dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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: 2017-07/txt/msg00889.txt.bz2 Content-length: 451 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D59521 --- Comment #7 from Yuri Gribov --- (In reply to Martin Li=C5=A1ka from comment #5) > Apart from that I added code that preserves > that probability in combine_predictions_for_bb. Yes, I did pretty much the same locally) > But still there's a missing piece that will rearrange switch statement so > that case 333 will be first: Right, I'll take it from there then. >>From gcc-bugs-return-568339-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 09:43:41 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 86717 invoked by alias); 11 Jul 2017 09:43: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 82705 invoked by uid 48); 11 Jul 2017 09:43:36 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/81390] New: ICE in to_reg_br_prob_base while compiling kernel Date: Tue, 11 Jul 2017 09:43:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone cf_reconfirmed_on everconfirmed 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: 2017-07/txt/msg00890.txt.bz2 Content-length: 1399 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81390 Bug ID: 81390 Summary: ICE in to_reg_br_prob_base while compiling kernel Product: gcc Version: 8.0 Status: WAITING Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: prathamesh3492 at gcc dot gnu.org CC: marxin at gcc dot gnu.org Target Milestone: --- Status: WAITING Last reconfirmed: 2017-07-11 CC: marxin at gcc dot gnu.org Ever confirmed: 1 Hi, Compiling kernel on x86_64 with allmodconfig results in following ICE: during GIMPLE pass: profile_estimate init/main.c: In function =E2=80=98mm_init=E2=80=99: init/main.c:1071:1: internal compiler error: in to_reg_br_prob_base, at profile-count.h:189 } ^ 0x65af83 profile_probability::to_reg_br_prob_base() const ../../gcc/gcc/profile-count.h:189 0x65af83 estimate_bb_frequencies(bool) ../../gcc/gcc/predict.c:3559 0xbdd8af tree_estimate_probability(bool) ../../gcc/gcc/predict.c:2828 0xbdd9f3 execute ../../gcc/gcc/predict.c:3701 Tested with r250102. Thanks, Prathamesh --- Comment #1 from Martin Li=C5=A1ka --- Can you please provide a pre-processed source file which is affected. Would= be easier to fix the issue. >>From gcc-bugs-return-568340-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 09:49:40 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 13219 invoked by alias); 11 Jul 2017 09:49: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 13164 invoked by uid 48); 11 Jul 2017 09:49:36 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/81389] _mm_cmpestri segfault on -O0 Date: Tue, 11 Jul 2017 09:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on 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: 2017-07/txt/msg00891.txt.bz2 Content-length: 837 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81389 Martin Li=C5=A1ka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Last reconfirmed| |2017-07-11 CC| |marxin at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from Martin Li=C5=A1ka --- As the signature of the intrinsic is: _mm_cmpestri (__m128i __X, int __LX, __m128i __Y, int __LY, const int __M) And as __m128i variables are aligned to 16 bytes boundary, thus then it sho= uld not be problem? Or can be problem if one casts an unaligned memory to (__m1= 28i *)? >>From gcc-bugs-return-568341-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 09:53:47 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 21648 invoked by alias); 11 Jul 2017 09: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 21597 invoked by uid 48); 11 Jul 2017 09:53:43 -0000 From: "trippels at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/81390] ICE in to_reg_br_prob_base while compiling kernel Date: Tue, 11 Jul 2017 09:53:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: trippels 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: 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: 2017-07/txt/msg00892.txt.bz2 Content-length: 470 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81390 Markus Trippelsdorf changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |trippels at gcc dot gnu.org --- Comment #2 from Markus Trippelsdorf --- dup of 81261? I'm also seeing the same ICE running the Boost testsuite. >>From gcc-bugs-return-568345-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 09:58:33 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 28386 invoked by alias); 11 Jul 2017 09:58: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 25118 invoked by uid 48); 11 Jul 2017 09:58:28 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/81391] Use of parenthesis disables warning about incorrect size parameter Date: Tue, 11 Jul 2017 09:58:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 5.4.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status 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: 2017-07/txt/msg00896.txt.bz2 Content-length: 346 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81391 Martin Li=C5=A1ka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 >>From gcc-bugs-return-568344-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 09:58:31 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 27842 invoked by alias); 11 Jul 2017 09:58: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 24086 invoked by uid 48); 11 Jul 2017 09:58:27 -0000 From: "trippels at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/81318] [8 regression] ICE in to_reg_br_prob_base, at profile-count.h:189 Date: Tue, 11 Jul 2017 09:58:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: trippels at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: 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: 2017-07/txt/msg00895.txt.bz2 Content-length: 468 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81318 Markus Trippelsdorf changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |prathamesh3492 at gcc dot = gnu.org --- Comment #5 from Markus Trippelsdorf --- *** Bug 81390 has been marked as a duplicate of this bug. *** >>From gcc-bugs-return-568342-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 09:58:14 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 14423 invoked by alias); 11 Jul 2017 09:58: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 7967 invoked by uid 48); 11 Jul 2017 09:58:08 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/81391] Use of parenthesis disables warning about incorrect size parameter Date: Tue, 11 Jul 2017 09:58:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 5.4.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cf_reconfirmed_on cc cf_known_to_work 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: 2017-07/txt/msg00893.txt.bz2 Content-length: 651 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81391 Martin Li=C5=A1ka changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2017-7-11 CC| |marxin at gcc dot gnu.org Known to work| |8.0 Known to fail| |5.4.0, 6.4.0, 7.1.0 --- Comment #1 from Martin Li=C5=A1ka --- Works on trunk starting from r248811. Is the revision a subject of backport= ing? >>From gcc-bugs-return-568343-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 09:58:30 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 27317 invoked by alias); 11 Jul 2017 09:58:30 -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 23235 invoked by uid 48); 11 Jul 2017 09:58:26 -0000 From: "trippels at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/81390] ICE in to_reg_br_prob_base while compiling kernel Date: Tue, 11 Jul 2017 09:58:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: trippels at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: 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: 2017-07/txt/msg00894.txt.bz2 Content-length: 523 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81390 Markus Trippelsdorf changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Markus Trippelsdorf --- Sorry, I meant PR81318 *** This bug has been marked as a duplicate of bug 81318 *** >>From gcc-bugs-return-568346-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 09:59:26 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 51391 invoked by alias); 11 Jul 2017 09:59: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 51294 invoked by uid 48); 11 Jul 2017 09:59:22 -0000 From: "trippels at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/81318] [8 regression] ICE in to_reg_br_prob_base, at profile-count.h:189 Date: Tue, 11 Jul 2017 09:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: trippels at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc target_milestone 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: 2017-07/txt/msg00897.txt.bz2 Content-length: 664 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81318 Markus Trippelsdorf changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-07-11 CC| |trippels at gcc dot gnu.org Target Milestone|--- |8.0 Ever confirmed|0 |1 --- Comment #6 from Markus Trippelsdorf --- Also happens when compiling the Boost testsuite. >>From gcc-bugs-return-568347-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 10:02:11 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 54889 invoked by alias); 11 Jul 2017 10:02: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 54441 invoked by uid 48); 11 Jul 2017 10:01:59 -0000 From: "trippels at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/81318] [8 regression] ICE in to_reg_br_prob_base, at profile-count.h:189 Date: Tue, 11 Jul 2017 10:02:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: trippels at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.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: 2017-07/txt/msg00898.txt.bz2 Content-length: 197 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81318 --- Comment #7 from Markus Trippelsdorf --- Also see https://gcc.gnu.org/ml/gcc-regression/2017-07/msg00144.html >>From gcc-bugs-return-568348-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 10:03:13 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 59510 invoked by alias); 11 Jul 2017 10:03: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 59386 invoked by uid 48); 11 Jul 2017 10:03:08 -0000 From: "trippels at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/81318] [8 regression] ICE in to_reg_br_prob_base, at profile-count.h:189 Date: Tue, 11 Jul 2017 10:03:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: trippels 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: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: keywords priority 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: 2017-07/txt/msg00899.txt.bz2 Content-length: 365 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81318 Markus Trippelsdorf changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ice-on-valid-code Priority|P3 |P1 >>From gcc-bugs-return-568349-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 10:05:18 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 65781 invoked by alias); 11 Jul 2017 10:05: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 65659 invoked by uid 48); 11 Jul 2017 10:05:14 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81369] [8 Regression] ICE in generate_code_for_partition Date: Tue, 11 Jul 2017 10:05:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc 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: 2017-07/txt/msg00900.txt.bz2 Content-length: 660 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81369 Martin Li=C5=A1ka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-07-11 CC| |amker at gcc dot gnu.org, | |marxin at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from Martin Li=C5=A1ka --- Confirmed, started with r249994. >>From gcc-bugs-return-568350-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 10:07:12 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 67519 invoked by alias); 11 Jul 2017 10:07: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 67454 invoked by uid 48); 11 Jul 2017 10:07:06 -0000 From: "amker at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81369] [8 Regression] ICE in generate_code_for_partition Date: Tue, 11 Jul 2017 10:07:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: amker at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: amker at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: 2017-07/txt/msg00901.txt.bz2 Content-length: 400 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81369 amker at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |amker at gcc dot gn= u.org --- Comment #2 from amker at gcc dot gnu.org --- Thanks for reporting. I will investigate it. >>From gcc-bugs-return-568351-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 10:11:38 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 55322 invoked by alias); 11 Jul 2017 10:11: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 50126 invoked by uid 48); 11 Jul 2017 10:11:33 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/81367] [5/6 Regression] ICE in gfc_typenode_for_spec, at fortran/trans-types.c:1086 Date: Tue, 11 Jul 2017 10:11:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 5.4.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc cf_known_to_work short_desc everconfirmed cf_known_to_fail Message-ID: 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: 2017-07/txt/msg00902.txt.bz2 Content-length: 1068 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81367 Martin Li=C5=A1ka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-07-11 CC| |kargl at gcc dot gnu.org, | |marxin at gcc dot gnu.org Known to work| |7.1.0, 8.0 Summary|internal compiler error: in |[5/6 Regression] ICE in |gfc_typenode_for_spec, at |gfc_typenode_for_spec, at |fortran/trans-types.c:1086 |fortran/trans-types.c:1086 Ever confirmed|0 |1 Known to fail| |5.4.0, 6.4.0 --- Comment #1 from Martin Li=C5=A1ka --- Confirmed, was fixed on trunk by r240191 and was introduced in time of GCC 5 and 6 by r229287. >>From gcc-bugs-return-568352-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 10:14:25 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 52413 invoked by alias); 11 Jul 2017 10:14:25 -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 46598 invoked by uid 48); 11 Jul 2017 10:14:17 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81365] [7/8 Regression] GCC miscompiles swap Date: Tue, 11 Jul 2017 10:14:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: alias, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 7.2 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: 2017-07/txt/msg00903.txt.bz2 Content-length: 463 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81365 Martin Li=C5=A1ka changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marxin at gcc dot gnu.org --- Comment #3 from Martin Li=C5=A1ka --- Introduced by unrelated commit which added early jump threading (r240221). >>From gcc-bugs-return-568353-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 10:19:18 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 23151 invoked by alias); 11 Jul 2017 10:19: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 23086 invoked by uid 48); 11 Jul 2017 10:19:14 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81354] [5/6 Regression] Segmentation fault in SSA Strength Reduction using -O3 Date: Tue, 11 Jul 2017 10:19:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 5.4.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc cf_known_to_work short_desc everconfirmed cf_known_to_fail Message-ID: 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: 2017-07/txt/msg00904.txt.bz2 Content-length: 1214 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81354 Martin Li=C5=A1ka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-07-11 CC| |marxin at gcc dot gnu.org, | |rguenth at gcc dot gnu.org Known to work| |4.5.4, 4.6.4, 4.7.4, 4.8.5, | |4.9.4, 7.1.0, 8.0 Summary|Segmentation fault in SSA |[5/6 Regression] |Strength Reduction using |Segmentation fault in SSA |-O3 |Strength Reduction using | |-O3 Ever confirmed|0 |1 Known to fail| |5.4.0, 6.4.0 --- Comment #1 from Martin Li=C5=A1ka --- Confirmed, fixed on trunk by r236440 and was introduced by r217914. Richi i= s it a subject of backport maybe? >>From gcc-bugs-return-568354-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 10:21:47 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 5926 invoked by alias); 11 Jul 2017 10:21: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 5839 invoked by uid 48); 11 Jul 2017 10:21:43 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/81355] SegFault when using attribute target dispatch with empty parameter Date: Tue, 11 Jul 2017 10: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: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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: 2017-07/txt/msg00905.txt.bz2 Content-length: 667 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81355 Martin Li=C5=A1ka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2017-07-11 CC| |marxin at gcc dot gnu.org Assignee|unassigned at gcc dot gnu.org |marxin at gcc dot g= nu.org Ever confirmed|0 |1 --- Comment #1 from Martin Li=C5=A1ka --- Confirmed, I'll fix that! >>From gcc-bugs-return-568355-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 10:24:53 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 23510 invoked by alias); 11 Jul 2017 10:24: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 23383 invoked by uid 48); 11 Jul 2017 10:24:39 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/81342] LTO: lto1: internal compiler error: Segmentation fault Date: Tue, 11 Jul 2017 10:24:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: lto X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on 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: 2017-07/txt/msg00906.txt.bz2 Content-length: 675 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81342 Martin Li=C5=A1ka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Last reconfirmed| |2017-07-11 CC| |marxin at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from Martin Li=C5=A1ka --- Can you please provide info which project is affected (I guess Linux kernel= ). Can you help me how to reproduce that? >>From gcc-bugs-return-568356-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 10:25:39 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 26131 invoked by alias); 11 Jul 2017 10:25: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 25958 invoked by uid 48); 11 Jul 2017 10:25:33 -0000 From: "dominiq at lps dot ens.fr" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/81367] [5/6 Regression] ICE in gfc_typenode_for_spec, at fortran/trans-types.c:1086 Date: Tue, 11 Jul 2017 10:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 5.4.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dominiq at lps dot ens.fr X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: 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: 2017-07/txt/msg00907.txt.bz2 Content-length: 1525 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81367 --- Comment #2 from Dominique d'Humieres --- AFAICT this is fixed in 5.4.1 and 6.4.0: % gfc5 pr81367.f90 pr81367.f90:5:18: character(len=3Df)::fname 1 Error: Scalar INTEGER expression expected at (1) % gfc5 -v Using built-in specs. COLLECT_GCC=3Dgfc5 COLLECT_LTO_WRAPPER=3D/opt/gcc/gcc5wr/libexec/gcc/x86_64-apple-darwin16.6.0= /5.4.1/lto-wrapper Target: x86_64-apple-darwin16.6.0 Configured with: ../5_work/configure --prefix=3D/opt/gcc/gcc5wr --enable-languages=3Dc,c++,fortran,objc,obj-c++,ada,java,lto --with-gmp=3D/opt/mp-new --with-system-zlib --with-isl=3D/opt/mp-new --enab= le-lto --enable-plugin Thread model: posix gcc version 5.4.1 20170604 [5 branch revision 248859p3] (GCC)=20 % gfortran-fsf-6 pr81367.f90 pr81367.f90:5:18: character(len=3Df)::fname 1 Error: Scalar INTEGER expression expected at (1) % gfortran-fsf-6 -v Using built-in specs. COLLECT_GCC=3Dgfortran-fsf-6 COLLECT_LTO_WRAPPER=3D/sw64/lib/gcc6/libexec/gcc/x86_64-apple-darwin16.6.0/= 6.4.0/lto-wrapper Target: x86_64-apple-darwin16.6.0 Configured with: ../gcc-6.4.0/configure --prefix=3D/sw64 --prefix=3D/sw64/l= ib/gcc6 --mandir=3D/sw64/share/man --infodir=3D/sw64/lib/gcc6/info --enable-languages=3Dc,c++,fortran,lto,objc,obj-c++,java --with-gmp=3D/sw64 --with-libiconv-prefix=3D/sw64 --with-isl=3D/sw64 --with-mpc=3D/sw64 --with-system-zlib --program-suffix=3D-fsf-6 Thread model: posix gcc version 6.4.0 (GCC) >>From gcc-bugs-return-568357-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 10:29:32 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 51907 invoked by alias); 11 Jul 2017 10:29: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 51817 invoked by uid 48); 11 Jul 2017 10:29:27 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/81367] [5 Regression] ICE in gfc_typenode_for_spec, at fortran/trans-types.c:1086 Date: Tue, 11 Jul 2017 10:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 5.4.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: 2017-07/txt/msg00908.txt.bz2 Content-length: 761 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81367 Martin Li=C5=A1ka changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |5.1.0, 5.2.0, 6.3.0, 6.4.0 Summary|[5/6 Regression] ICE in |[5 Regression] ICE in |gfc_typenode_for_spec, at |gfc_typenode_for_spec, at |fortran/trans-types.c:1086 |fortran/trans-types.c:1086 Known to fail|6.4.0 |5.3.0, 6.1.0, 6.2.0 --- Comment #3 from Martin Li=C5=A1ka --- Yep, 5.1 and 5.2 are fine, however 5.3 and 5.4 not. And yes, 6.4 is fine, sorry. >>From gcc-bugs-return-568358-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 10:31:59 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 61297 invoked by alias); 11 Jul 2017 10:31: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 61161 invoked by uid 48); 11 Jul 2017 10:31:54 -0000 From: "hubicka at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/81033] [8 Regression] Revision r249019 breaks bootstrap on darwin Date: Tue, 11 Jul 2017 10:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: bootstrap X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: build, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: hubicka at gcc dot gnu.org X-Bugzilla-Status: REOPENED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: 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: 2017-07/txt/msg00909.txt.bz2 Content-length: 357 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81033 --- Comment #24 from Jan Hubicka --- I think the patch still need to be updated to correctly handle the symbols whose names are parethetised which was mentioned on the IRC (weird thing th= at seems to be used in objC++ API). That should fix good part of the fallout = too. >>From gcc-bugs-return-568359-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 10:32:39 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 90303 invoked by alias); 11 Jul 2017 10:32: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 90191 invoked by uid 48); 11 Jul 2017 10:32:34 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/81319] ICE in output_operand_lossage at final.c Date: Tue, 11 Jul 2017 10:32:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: ice-on-invalid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc 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: 2017-07/txt/msg00910.txt.bz2 Content-length: 600 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81319 Martin Li=C5=A1ka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-07-11 CC| |marxin at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from Martin Li=C5=A1ka --- Confirmed, all releases I have do ICE (4.5.0+). >>From gcc-bugs-return-568360-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 10:33:55 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 109368 invoked by alias); 11 Jul 2017 10:33: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 107756 invoked by uid 48); 11 Jul 2017 10:33:50 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/81271] gcc/cp/lex.c:116: wrong condition ? Date: Tue, 11 Jul 2017 10:33:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cf_reconfirmed_on 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: 2017-07/txt/msg00911.txt.bz2 Content-length: 562 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81271 Martin Li=C5=A1ka changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2017-7-11 CC| |marxin at gcc dot gnu.org, | |nathan at gcc dot gnu.org --- Comment #1 from Martin Li=C5=A1ka --- Adding Nathan, the author of the code. >>From gcc-bugs-return-568361-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 10:35:03 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 113832 invoked by alias); 11 Jul 2017 10:35: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 113692 invoked by uid 48); 11 Jul 2017 10:34:59 -0000 From: "dominiq at lps dot ens.fr" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/81367] [5 Regression] ICE in gfc_typenode_for_spec, at fortran/trans-types.c:1086 Date: Tue, 11 Jul 2017 10:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 5.4.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dominiq at lps dot ens.fr X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cf_known_to_work 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: 2017-07/txt/msg00912.txt.bz2 Content-length: 475 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81367 Dominique d'Humieres changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |5.4.1 --- Comment #4 from Dominique d'Humieres --- Since it is also fixed in 5.4.1, i.e., the future 5.5.0, I think this PR co= uld be closed as FIXED. >>From gcc-bugs-return-568362-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 10:42:27 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 13060 invoked by alias); 11 Jul 2017 10:42: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 12672 invoked by uid 48); 11 Jul 2017 10:42:22 -0000 From: "cody at codygray dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/81392] New: Improve diagnostics for [[fallthrough]] attribute that is missing a semicolon Date: Tue, 11 Jul 2017 10: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: 8.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: cody at codygray 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: 2017-07/txt/msg00913.txt.bz2 Content-length: 1931 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81392 Bug ID: 81392 Summary: Improve diagnostics for [[fallthrough]] attribute that is missing a semicolon Product: gcc Version: 8.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: cody at codygray dot com Target Milestone: --- The C++1z/C++17 draft standard introduces a [[fallthrough]] attribute to explicitly document that fall-through behavior is intended in a switch-case block. This works in conjunction with G++'s -Wimplicit-fallthrough option, which g= ives a warning about potentially unintended fall-through behaviors. The [[fallthrough]] attribute is required to be applied to an empty stateme= nt (see http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0188r1.pdf), = and therefore requires a terminating semicolon. However, forgetting that semicolon is a common error. With the following co= de: #include int main() { switch (0) { case 0: std::cout << "a\n"; [[fallthrough]] case 1: std::cout << "b\n"; break; } } G++ (7.1 and the current trunk of 8.0) issues the following warning: warning: this statement may fall through [-Wimplicit-fallthrough=3D] std::cout << "a\n"; ~~~~~~~~~~^~~~~~~~ This is less helpful than it could be. The current Clang trunk provides a substantially more helpful error message in this case: error: fallthrough attribute is only allowed on empty statements [[fallthrough]] ^ note: did you forget ';'? [[fallthrough]] ^ ; It would be nice to have something similar in G++. >>From gcc-bugs-return-568363-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 10:46:13 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 24471 invoked by alias); 11 Jul 2017 10:46: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 24294 invoked by uid 48); 11 Jul 2017 10:46:07 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/81367] [5 Regression] ICE in gfc_typenode_for_spec, at fortran/trans-types.c:1086 Date: Tue, 11 Jul 2017 10:46:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 5.4.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: 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: 2017-07/txt/msg00914.txt.bz2 Content-length: 439 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81367 Martin Li=C5=A1ka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #5 from Martin Li=C5=A1ka --- Yep, thanks. >>From gcc-bugs-return-568364-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 10:56:43 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 90754 invoked by alias); 11 Jul 2017 10:56:43 -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 90429 invoked by uid 48); 11 Jul 2017 10:56:39 -0000 From: "trippels at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/81318] [8 regression] ICE in to_reg_br_prob_base, at profile-count.h:189 Date: Tue, 11 Jul 2017 10:56:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: trippels 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: 8.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: 2017-07/txt/msg00915.txt.bz2 Content-length: 783 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81318 --- Comment #8 from Markus Trippelsdorf --- Reduced Boost testcase: struct A; struct B { typedef A *type; }; struct C { B::type operator->(); }; struct D { struct F { F(void(void *), F *, void()); }; template struct J : F { FunT m_Function; J(FunT) : F(m_fn1, 0, 0) {} static void m_fn1(void *) { static_cast(0)->m_Function(); } }; F *m_pImpl; template D(FunT p1) : m_pImpl(new J(p1)) {} }; struct A { void m_fn2(D); }; struct G { void operator()() { throw; } }; struct H { void operator()() try { G()(); } catch (int) { } }; struct I { void operator()() { H()(); } }; void fn1() { I a; C b; b->m_fn2(a); } >>From gcc-bugs-return-568365-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 11:01:12 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 127357 invoked by alias); 11 Jul 2017 11:01: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 124805 invoked by uid 48); 11 Jul 2017 11:01:04 -0000 From: "mpolacek at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/81364] Bogus -Wmultistatement-macros warning Date: Tue, 11 Jul 2017 11:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: preprocessor X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mpolacek at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.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: 2017-07/txt/msg00916.txt.bz2 Content-length: 228 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81364 --- Comment #2 from Marek Polacek --- C++ doesn't warn. The problem is that we shouldn't warn (in the C FE) when= a guard is followed by '{'. >>From gcc-bugs-return-568366-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 11:23:25 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 120927 invoked by alias); 11 Jul 2017 11:23: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 119005 invoked by uid 48); 11 Jul 2017 11:23:20 -0000 From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: =?UTF-8?B?W0J1ZyBzYW5pdGl6ZXIvODEwNjZdIHNhbml0aXplcl9zdG9wdGhld29ybGRf?= =?UTF-8?B?bGludXhfbGliY2RlcC5jYzoyNzY6MjI6IGVycm9yOiBhZ2dyZWdhdGUg4oCY?= =?UTF-8?B?c2lnYWx0c3RhY2sgaGFuZGxlcl9zdGFja+KAmSBoYXMgaW5jb21wbGV0ZSB0?= =?UTF-8?B?eXBlIGFuZCBjYW5ub3QgYmUgZGVmaW5lZA==?= Date: Tue, 11 Jul 2017 11:23:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: 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: 2017-07/txt/msg00917.txt.bz2 Content-length: 182 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81066 --- Comment #12 from Jakub Jelinek --- I've filed https://reviews.llvm.org/D35246 upstream for this. >>From gcc-bugs-return-568367-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 11:40:03 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 2320 invoked by alias); 11 Jul 2017 11:40: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 2242 invoked by uid 48); 11 Jul 2017 11:39:58 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/81392] Improve diagnostics for [[fallthrough]] attribute that is missing a semicolon Date: Tue, 11 Jul 2017 11:40:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed Message-ID: 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: 2017-07/txt/msg00918.txt.bz2 Content-length: 402 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81392 Jonathan Wakely changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-07-11 Ever confirmed|0 |1 >>From gcc-bugs-return-568368-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 11:50:48 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 53252 invoked by alias); 11 Jul 2017 11:50: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 53164 invoked by uid 48); 11 Jul 2017 11:50:43 -0000 From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug go/81393] New: Bootstrap failure on s390x-linux while building libgo against recent glibc Date: Tue, 11 Jul 2017 11:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: go X-Bugzilla-Version: 7.1.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: ian at airs dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-07/txt/msg00919.txt.bz2 Content-length: 2274 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81393 Bug ID: 81393 Summary: Bootstrap failure on s390x-linux while building libgo against recent glibc Product: gcc Version: 7.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: go Assignee: ian at airs dot com Reporter: jakub at gcc dot gnu.org CC: cmang at google dot com Target Milestone: --- Current 7 branch doesn't build against recent glibc, not just because of libsanitizer issues tracked in another PR, but also due to: ../../../../libgo/go/syscall/syscall_linux_s390.go:16:16: error: reference = to undefined name =E2=80=98PTRACE_GETREGS=E2=80=99 return ptrace(PTRACE_GETREGS, pid, 0, uintptr(unsafe.Pointer(regsout))) ^ ../../../../libgo/go/syscall/syscall_linux_s390.go:20:16: error: reference = to undefined name =E2=80=98PTRACE_SETREGS=E2=80=99 return ptrace(PTRACE_SETREGS, pid, 0, uintptr(unsafe.Pointer(regs))) ^ make[6]: *** [Makefile:3331: syscall.lo] Error 1 This is because glibc has removed those in: https://sourceware.org/bugzilla/show_bug.cgi?id=3D21539 claiming the kernel never supported them and it never worked. Thus, I think syscall_linux_s390{,x}.go should probably use PTRACE_GETREGSET and PTRACE_SETREGSET instead. Elsewhere I found static long our_ptrace_getregs(pid_t pid, struct USER_REGS_TYPE *regs) { #ifdef AARCH64 struct iovec iovec =3D { regs, sizeof(*regs) }; return our_ptrace(PTRACE_GETREGSET, pid, (void *)NT_PRSTATUS, &iovec); #else return our_ptrace(PTRACE_GETREGS, pid, NULL, regs); #endif } static long our_ptrace_setregs(pid_t pid, struct USER_REGS_TYPE *regs) { #ifdef AARCH64 struct iovec iovec =3D { regs, sizeof(*regs) }; return our_ptrace(PTRACE_SETREGSET, pid, (void *)NT_PRSTATUS, &iovec); #else return our_ptrace(PTRACE_SETREGS, pid, NULL, regs); #endif } where aarch64 doesn't support PTRACE_SETREGS/GETREGS similarly to s390{,x} (though for some reason doesn't provide any syscall_linux_{arm64,aarch64}.g= o or whatever). In sysinfo.go I see PTRACE_{G,S}ETREGSET defined, but not NT_PRSTATUS (which is 1, in elf.h?), and I see _iovec type. >>From gcc-bugs-return-568369-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 11:52:52 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 56257 invoked by alias); 11 Jul 2017 11:52:52 -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 56154 invoked by uid 55); 11 Jul 2017 11:52:48 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/80316] std::promise treats no shared state as undefined Date: Tue, 11 Jul 2017 11:52:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 7.0.1 X-Bugzilla-Keywords: patch X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: redi at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: 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: 2017-07/txt/msg00920.txt.bz2 Content-length: 2180 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D80316 --- Comment #3 from Jonathan Wakely --- Author: redi Date: Tue Jul 11 11:52:14 2017 New Revision: 250126 URL: https://gcc.gnu.org/viewcvs?rev=3D250126&root=3Dgcc&view=3Drev Log: PR libstdc++/80316 make promise::set_value throw no_state error Backport from mainline 2017-04-21 Jonathan Wakely PR libstdc++/80316 * include/std/future (_State_baseV2::_Setter::operator()): Remove _S_check calls that are done after the pointer to the shared state = is already dereferenced. (_State_baseV2::_Setter<_Res, void>): Define specialization for void as partial specialization so it can be defined within the definition of _State_baseV2. (_State_baseV2::__setter): Call _S_check. (_State_baseV2::__setter(promise*)): Add overload for use by promise::set_value and promise::set_value_at_thread_exi= t. (promise, promise, promise): Make _State a friend. (_State_baseV2::_Setter): Remove explicit specializatio= n. (promise::set_value, promise::set_value_at_thread_exit): Use new __setter overload. * testsuite/30_threads/promise/members/at_thread_exit2.cc: New test. * testsuite/30_threads/promise/members/set_exception.cc: Test promise and promise specializations. * testsuite/30_threads/promise/members/set_exception2.cc: Likewise. Test for no_state error condition. * testsuite/30_threads/promise/members/set_value2.cc: Likewise. Added: =20=20=20 branches/gcc-7-branch/libstdc++-v3/testsuite/30_threads/promise/members/at_= thread_exit2.cc Modified: branches/gcc-7-branch/libstdc++-v3/ChangeLog branches/gcc-7-branch/libstdc++-v3/include/std/future =20=20=20 branches/gcc-7-branch/libstdc++-v3/testsuite/30_threads/promise/members/set= _exception.cc =20=20=20 branches/gcc-7-branch/libstdc++-v3/testsuite/30_threads/promise/members/set= _exception2.cc =20=20=20 branches/gcc-7-branch/libstdc++-v3/testsuite/30_threads/promise/members/set= _value2.cc >>From gcc-bugs-return-568370-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 12:10:55 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 28432 invoked by alias); 11 Jul 2017 12:10: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 28345 invoked by uid 48); 11 Jul 2017 12:10:50 -0000 From: "f.heckenbach@fh-soft.de" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/81394] New: wrong "useless cast" message in inheriting constructor Date: Tue, 11 Jul 2017 12: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: 6.3.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: f.heckenbach@fh-soft.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: 2017-07/txt/msg00921.txt.bz2 Content-length: 933 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81394 Bug ID: 81394 Summary: wrong "useless cast" message in inheriting constructor Product: gcc Version: 6.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: f.heckenbach@fh-soft.de Target Milestone: --- % cat t.cpp struct a { template a (T && v) { } }; struct b: a { using a::a; }; int main () { b { "foo" }; } % g++ -Wuseless-cast t.cpp t.cpp: In constructor 'b::b(T&&) [with T =3D const char (&)[4]]': t.cpp:8:12: warning: useless cast to type 'const char (&)[4]' [-Wuseless-ca= st] using a::a; ^ t.cpp: In function 'int main()': t.cpp:13:13: note: synthesized method 'b::b(T&&) [with T =3D const char (&)= [4]]' first required here=20 b { "foo" }; ^ >>From gcc-bugs-return-568371-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 12:12:57 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 30730 invoked by alias); 11 Jul 2017 12:12: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 30683 invoked by uid 48); 11 Jul 2017 12:12:53 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/81395] New: basic_filebuf::overflow recurses and overflows stack Date: Tue, 11 Jul 2017 12:12:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-07/txt/msg00922.txt.bz2 Content-length: 1870 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81395 Bug ID: 81395 Summary: basic_filebuf::overflow recurses and overflows stack Product: gcc Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: redi at gcc dot gnu.org Target Milestone: --- This program goes into an infinite recursion in basic_filebuf::overflow: #include #include using std::memset; int main() { { std::ofstream s("test.txt"); char data[BUFSIZ]; memset(data, 'A', sizeof(data)); s.write(data, sizeof(data)); } std::fstream s("test.txt"); char buf[BUFSIZ]; memset(buf, 0, sizeof(buf)); s.read(buf, sizeof(buf)); #ifdef FIX s.seekg(sizeof(buf)); #endif s << 'B'; } The standard requires the seek performed when FIX is defined, so we're allo= wed to give unexpected results. Even so, it would be preferable to not crash wh= en that's missing. The problem is that the write calls overflow which starts with: if (__testout) { if (_M_reading) { _M_destroy_pback(); const int __gptr_off =3D _M_get_ext_pos(_M_state_last); if (_M_seek(__gptr_off, ios_base::cur, _M_state_last) =3D=3D pos_type(off_type(-1))) return __ret; } That call to _M_seek calls _M_terminate_output which starts with: // Part one: update the output sequence. bool __testvalid =3D true; if (this->pbase() < this->pptr()) { const int_type __tmp =3D this->overflow(); if (traits_type::eq_int_type(__tmp, traits_type::eof())) __testvalid =3D false; } So we go back to overflow() and then recurse. >>From gcc-bugs-return-568372-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 12:18:31 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 40036 invoked by alias); 11 Jul 2017 12:18: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 39963 invoked by uid 48); 11 Jul 2017 12:18:26 -0000 From: "nathan at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/81271] gcc/cp/lex.c:116: wrong condition ? Date: Tue, 11 Jul 2017 12:18:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: nathan at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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: 2017-07/txt/msg00923.txt.bz2 Content-length: 540 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81271 Nathan Sidwell changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #2 from Nathan Sidwell --- Either would be fine -- I was thinking of these things as bits not bools, s= o & made sense, but if && shuts the compiler up ... >>From gcc-bugs-return-568373-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 12:36:45 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 105530 invoked by alias); 11 Jul 2017 12:36: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 97839 invoked by uid 48); 11 Jul 2017 12:36:38 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/81395] basic_filebuf::overflow recurses and overflows stack Date: Tue, 11 Jul 2017 12:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed Message-ID: 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: 2017-07/txt/msg00924.txt.bz2 Content-length: 2354 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81395 Jonathan Wakely changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-07-11 Ever confirmed|0 |1 --- Comment #1 from Jonathan Wakely --- (In reply to Jonathan Wakely from comment #0) > The problem is that the write calls overflow which starts with: Correction: the destructor calls overflow in this testcase. In the original testcase from a customer there was a write of BUFSIZ, which triggered overf= low after filling the put area. A more direct way to reproduce it is by changing the final s << 'B'; to: s.write("B", 1); s.flush(); I can prevent the recursion with either: @@ -515,6 +515,7 @@ if (_M_reading) { _M_destroy_pback(); + _M_reading =3D false; const int __gptr_off =3D _M_get_ext_pos(_M_state_last); if (_M_seek(__gptr_off, ios_base::cur, _M_state_last) =3D=3D pos_type(off_type(-1))) or: @@ -920,7 +925,7 @@ { // Part one: update the output sequence. bool __testvalid =3D true; - if (this->pbase() < this->pptr()) + if (this->pbase() < this->pptr() && __builtin_expect(!_M_reading, 1)) { const int_type __tmp =3D this->overflow(); if (traits_type::eq_int_type(__tmp, traits_type::eof())) But why are we getting into this state anyway? We have a non-empty output sequence when _M_reading is true, meaning we're in the middle of an uncommi= tted read. At the end of basic_filebuf::xsgetn after the read we do: if (__n =3D=3D 0) { _M_set_buffer(0); _M_reading =3D true; } And _M_set_buffer(0) on a bidirectional filebuf sets up the put area: if (__testout && __off =3D=3D 0 && _M_buf_size > 1 ) this->setp(_M_buf, _M_buf + _M_buf_size - 1); else this->setp(0, 0); This means the next write inserts straight into the put area, and then the = next overflow() finds that _M_reading is true but there is also a pending output sequence. >>From gcc-bugs-return-568375-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 12:39:51 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 33129 invoked by alias); 11 Jul 2017 12:39: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 30980 invoked by uid 48); 11 Jul 2017 12:39:47 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/80316] std::promise treats no shared state as undefined Date: Tue, 11 Jul 2017 12:39:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 7.0.1 X-Bugzilla-Keywords: patch X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: redi at gcc dot gnu.org X-Bugzilla-Target-Milestone: 6.5 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution target_milestone 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: 2017-07/txt/msg00926.txt.bz2 Content-length: 555 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D80316 Jonathan Wakely changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED Target Milestone|--- |6.5 Known to fail| |6.4.0, 7.1.0 --- Comment #5 from Jonathan Wakely --- Fixed for 6.5 and 7.2 >>From gcc-bugs-return-568374-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 12:39:13 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 115432 invoked by alias); 11 Jul 2017 12:39: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 108461 invoked by uid 55); 11 Jul 2017 12:39:08 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/80316] std::promise treats no shared state as undefined Date: Tue, 11 Jul 2017 12:39:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 7.0.1 X-Bugzilla-Keywords: patch X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: redi at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: 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: 2017-07/txt/msg00925.txt.bz2 Content-length: 2180 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D80316 --- Comment #4 from Jonathan Wakely --- Author: redi Date: Tue Jul 11 12:38:35 2017 New Revision: 250131 URL: https://gcc.gnu.org/viewcvs?rev=3D250131&root=3Dgcc&view=3Drev Log: PR libstdc++/80316 make promise::set_value throw no_state error Backport from mainline 2017-04-21 Jonathan Wakely PR libstdc++/80316 * include/std/future (_State_baseV2::_Setter::operator()): Remove _S_check calls that are done after the pointer to the shared state = is already dereferenced. (_State_baseV2::_Setter<_Res, void>): Define specialization for void as partial specialization so it can be defined within the definition of _State_baseV2. (_State_baseV2::__setter): Call _S_check. (_State_baseV2::__setter(promise*)): Add overload for use by promise::set_value and promise::set_value_at_thread_exi= t. (promise, promise, promise): Make _State a friend. (_State_baseV2::_Setter): Remove explicit specializatio= n. (promise::set_value, promise::set_value_at_thread_exit): Use new __setter overload. * testsuite/30_threads/promise/members/at_thread_exit2.cc: New test. * testsuite/30_threads/promise/members/set_exception.cc: Test promise and promise specializations. * testsuite/30_threads/promise/members/set_exception2.cc: Likewise. Test for no_state error condition. * testsuite/30_threads/promise/members/set_value2.cc: Likewise. Added: =20=20=20 branches/gcc-6-branch/libstdc++-v3/testsuite/30_threads/promise/members/at_= thread_exit2.cc Modified: branches/gcc-6-branch/libstdc++-v3/ChangeLog branches/gcc-6-branch/libstdc++-v3/include/std/future =20=20=20 branches/gcc-6-branch/libstdc++-v3/testsuite/30_threads/promise/members/set= _exception.cc =20=20=20 branches/gcc-6-branch/libstdc++-v3/testsuite/30_threads/promise/members/set= _exception2.cc =20=20=20 branches/gcc-6-branch/libstdc++-v3/testsuite/30_threads/promise/members/set= _value2.cc >>From gcc-bugs-return-568376-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 12:52:31 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 10018 invoked by alias); 11 Jul 2017 12:52: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 2387 invoked by uid 48); 11 Jul 2017 12:52:26 -0000 From: "mpolacek at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/46742] -Wparentheses unexpectedly misses some cases Date: Tue, 11 Jul 2017 12:52:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 4.5.1 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: enhancement X-Bugzilla-Who: mpolacek at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: 2017-07/txt/msg00927.txt.bz2 Content-length: 497 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D46742 Marek Polacek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mpolacek at gcc dot gnu.org --- Comment #3 from Marek Polacek --- We only warn if the second operand is !APPEARS_TO_BE_BOOLEAN_EXPR_P, but 1 appears to be a boolean expression. >>From gcc-bugs-return-568377-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 12:54:23 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 122384 invoked by alias); 11 Jul 2017 12:54: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 118124 invoked by uid 48); 11 Jul 2017 12:54:18 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/81021] stack-use-after-scope false positive error with exceptions Date: Tue, 11 Jul 2017 12:54:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: marxin 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: 2017-07/txt/msg00928.txt.bz2 Content-length: 483 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81021 --- Comment #21 from Martin Li=C5=A1ka --- > The code uses user-level threads (makecontext/setcontext etc). It annotat= es > the new stack during the switch, see for example > https://github.com/scylladb/seastar/blob/master/core/thread.cc#L66. > Supposedly it's correct, but perhaps something is missing. Then it should be fine. Well, the patch you send just workaround the proble= m. I will dig in. >>From gcc-bugs-return-568378-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 12:58:13 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 55485 invoked by alias); 11 Jul 2017 12:58: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 50219 invoked by uid 48); 11 Jul 2017 12:58:09 -0000 From: "mpolacek at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/81320] -Wlogical-op diagnostic depends on comparison' order Date: Tue, 11 Jul 2017 12:58:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: mpolacek at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc short_desc 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: 2017-07/txt/msg00929.txt.bz2 Content-length: 646 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81320 Marek Polacek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mpolacek at gcc dot gnu.org Summary|[7/8] -Wlogical-op |-Wlogical-op diagnostic |diagnostic depends on |depends on comparison' |comparison' order |order --- Comment #1 from Marek Polacek --- Removing the regressions marker as this isn't a regression. >>From gcc-bugs-return-568379-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 13:25:12 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 119853 invoked by alias); 11 Jul 2017 13:25: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 116738 invoked by uid 48); 11 Jul 2017 13:25:06 -0000 From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81365] [7/8 Regression] GCC miscompiles swap Date: Tue, 11 Jul 2017 13:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: alias, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 7.2 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: 2017-07/txt/msg00930.txt.bz2 Content-length: 1805 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81365 Jakub Jelinek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #4 from Jakub Jelinek --- The optimization and thus the bug too has been introduced in r235208, i.e. PR70171. The check Andrew mentions has been added in r236079, i.e. PR71039. But it actually does something completely different than the check we need here, it makes sure that any SSA_NAMEs used in the lhs that we move earlier is avail= able there already. What we need here is something different. We already have: /* Check if we can move the loads. The def stmt of the virtual use needs to be in a different basic block dominating bb. When the def is an edge-inserted one we know it dominates us. */ vuse =3D gimple_vuse (use_stmt); def_stmt =3D SSA_NAME_DEF_STMT (vuse); if (!SSA_NAME_IS_DEFAULT_DEF (vuse) && (gimple_bb (def_stmt) =3D=3D bb || (gimple_bb (def_stmt) && !dominated_by_p (CDI_DOMINATORS, bb, gimple_bb (def_stmt))))) goto next; which makes sure we don't miscompile int h(int k, int i1, int j1) { int *f1; if(k) f1 =3D &i1; else f1 =3D &j1; i1 =3D 7; return *f1; } where the use_stmt has an earlier store that might modify it. That is sufficient for the reg type case, but for the aggregate, where we actually = move the aggregate store earlier - onto the edges - we also have to ensure that either there no memory loads between the PHI and use_stmt, or that the can't alias the lhs. >>From gcc-bugs-return-568381-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 13:27:43 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 24120 invoked by alias); 11 Jul 2017 13:27:43 -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 15782 invoked by uid 48); 11 Jul 2017 13:27:38 -0000 From: "mpolacek at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/81320] -Wlogical-op diagnostic depends on comparison' order Date: Tue, 11 Jul 2017 13:27:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: mpolacek at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on 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: 2017-07/txt/msg00932.txt.bz2 Content-length: 811 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81320 Marek Polacek changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-07-11 Ever confirmed|0 |1 --- Comment #2 from Marek Polacek --- We fail to warn in f2 because we compare the expression in the conditional sequentially, but that doesn't work due to left-to-right associativity: we compare i =3D=3D 0 with i =3D=3D 1 and then i =3D=3D 0 || i =3D=3D 1 with i =3D=3D 0. The fix would probably be to keep [low, high] pairs for every comparison and then compare the pairs. >>From gcc-bugs-return-568380-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 13:27:20 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 122878 invoked by alias); 11 Jul 2017 13:27: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 Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 116668 invoked by uid 48); 11 Jul 2017 13:27:15 -0000 From: "wschmidt at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/81348] PowerPC64: Code built with -mcpu=power9 hits SEGV in RTL split2 Date: Tue, 11 Jul 2017 13:27:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 7.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: wschmidt at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: meissner at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: 2017-07/txt/msg00931.txt.bz2 Content-length: 453 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81348 Bill Schmidt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #6 from Bill Schmidt --- Fixed everywhere...thanks, Mike! >>From gcc-bugs-return-568382-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 13:36:28 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 30865 invoked by alias); 11 Jul 2017 13:36:28 -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 25076 invoked by uid 48); 11 Jul 2017 13:36:23 -0000 From: "qrczakmk at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81396] New: Optimization of reading Little-Endian 64-bit number with portable code has a regression Date: Tue, 11 Jul 2017 13:36: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: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qrczakmk 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: 2017-07/txt/msg00933.txt.bz2 Content-length: 2380 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81396 Bug ID: 81396 Summary: Optimization of reading Little-Endian 64-bit number with portable code has a regression Product: gcc Version: 7.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: qrczakmk at gmail dot com Target Milestone: --- Consider this source code: #include uint64_t ReadLittleEndian64(uint64_t word) { const unsigned char* const ptr =3D reinterpret_cast(&word); return uint64_t{ptr[0]} | (uint64_t{ptr[1]} << 8) | (uint64_t{ptr[2]} << (8 * 2)) | (uint64_t{ptr[3]} << (8 * 3)) | (uint64_t{ptr[4]} << (8 * 4)) | (uint64_t{ptr[5]} << (8 * 5)) | (uint64_t{ptr[6]} << (8 * 6)) | (uint64_t{ptr[7]} << (8 * 7)); } gcc-6.3 generates good machine code on x86-64 with -O2: ReadLittleEndian64(unsigned long): mov rax, rdi ret gcc-7.1 leaves out one byte from the optimization: ReadLittleEndian64(unsigned long): movabs rax, 72057594037927935 and rax, rdi shr rdi, 56 sal rdi, 56 or rax, rdi ret Proof: https://gcc.godbolt.org/#z:OYLghAFBqd5QCxAYwPYBMCmBRdBLAF1QCcAaPECAKxAEZSBn= VAV2OUxAHIBSAJgGY8AO2QAbZlgDU3fgGEGBfEIIA6BDOzcADAEFtO5sIIA2ACwB9ApIBKmAIbo= AMoQKicQ/HaFmIh5WctJAHcSdABKaQB2ACF9SUk0IQVJZiS8YCFMdASEO2IAKgTUJKsABwJiaX4= AETj4%2BuJMI0xiUsaCc2Q7BRlZROTUhnTM7ORcgo0IPmMQ4nCZWN149tYhFKMAgm4Y8uJuAFZo= rQPayOqo2Tr6698Niy2dioPo2hPt897eyQAOCO3LpbXG5%2BEz3bbRXbPXhvM5VS5ySQQb6SQq8= MJ/SIAnRA4F3SzgyGHfgwj5yL5IlGSfjoi5XHG3fxgx57Q6mElw8nIwqmGn/OlAhmg/HM577dmf= BEUwr7XmY/m4xnCiFPQ7GcVkyVcyTGWVYnH1QWbAkq6KRdXw2SIrWRdELfTvfScMKkURcfacUhC= LhaD2oLiXXixQOSJisdjSAS0D0Eb1O50AaxA/H4KmTafTGeMLq4pg9Xs4PtIfs4HoYIC0pBjBad= pDgsCQaAAtqU8G4yBQIE2W22QMBjPxSAAzVsEFpliAAI1jpCbjcwygA8kJRABPaf4RrIAh4ABum= DL1fIykwrurztQ5TwxQPAFoF7xSyw2BxaM7T%2B7PdPiwAPb7GG9mJIwDIMg2qpoiuCECQEb8PQ= kiyKgzati0MGvtGsboqQibJqmGZ4cmWanrmn6HsWpblpWGG1jAiAoIh3YtOQlBdshxC9pE9DDqI= o7EOOU6HrO84EEuq7rngm7bnuB6Fs0p4%2Buel7Xlwd4PowT7sHQb5unmX5cL%2B/6AcBoGRCot= AQfgRCVHwsGkPB9GsTBaLoWeCZJim%2BH4dmnDEfmhZkYwFFVvJWmcKpvm%2BlwznBaQe68VeXq= mEAA%3D%3D >>From gcc-bugs-return-568383-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 14:09:31 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 32125 invoked by alias); 11 Jul 2017 14:09:30 -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 27917 invoked by uid 48); 11 Jul 2017 14:09:25 -0000 From: "grgoffe at yahoo dot com" To: gcc-bugs@gcc.gnu.org Subject: =?UTF-8?B?W0J1ZyBzYW5pdGl6ZXIvODEwNjZdIHNhbml0aXplcl9zdG9wdGhld29ybGRf?= =?UTF-8?B?bGludXhfbGliY2RlcC5jYzoyNzY6MjI6IGVycm9yOiBhZ2dyZWdhdGUg4oCY?= =?UTF-8?B?c2lnYWx0c3RhY2sgaGFuZGxlcl9zdGFja+KAmSBoYXMgaW5jb21wbGV0ZSB0?= =?UTF-8?B?eXBlIGFuZCBjYW5ub3QgYmUgZGVmaW5lZA==?= Date: Tue, 11 Jul 2017 14:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: normal X-Bugzilla-Who: grgoffe at yahoo dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: 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: 2017-07/txt/msg00934.txt.bz2 Content-length: 232 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81066 --- Comment #13 from George R. Goffe --- Jakub, I have built gcc with itself... including your mod... That appears to have worked as well. George... >>From gcc-bugs-return-568384-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 14:29:54 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 13258 invoked by alias); 11 Jul 2017 14:29: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 7648 invoked by uid 48); 11 Jul 2017 14:29:50 -0000 From: "seurer at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/81386] [8 regression] libgomp.fortran/appendix-a/a.16.1.f90 fails starting with 249424 Date: Tue, 11 Jul 2017 14:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libgomp X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: seurer at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: 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: 2017-07/txt/msg00935.txt.bz2 Content-length: 1373 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81386 --- Comment #1 from seurer at gcc dot gnu.org --- I looked back through the tester logs and noticed that the test case doesn't always fail and there are two different failures and always with -O3 PASS: libgomp.fortran/appendix-a/a.16.1.f90 -O0 (test for excess errors) PASS: libgomp.fortran/appendix-a/a.16.1.f90 -O0 execution test PASS: libgomp.fortran/appendix-a/a.16.1.f90 -O1 (test for excess errors) PASS: libgomp.fortran/appendix-a/a.16.1.f90 -O1 execution test PASS: libgomp.fortran/appendix-a/a.16.1.f90 -O2 (test for excess errors) PASS: libgomp.fortran/appendix-a/a.16.1.f90 -O2 execution test PASS: libgomp.fortran/appendix-a/a.16.1.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess errors) FAIL: libgomp.fortran/appendix-a/a.16.1.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test PASS: libgomp.fortran/appendix-a/a.16.1.f90 -O3 -g (test for excess erro= rs) FAIL: libgomp.fortran/appendix-a/a.16.1.f90 -O3 -g execution test PASS: libgomp.fortran/appendix-a/a.16.1.f90 -Os (test for excess errors) Oddly in many test runs the two errors occur equally often (about 87% of the time for each one) but not always together. Neither error occurs in just 1= .5% of the runs. >>From gcc-bugs-return-568385-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 14:54:12 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 123291 invoked by alias); 11 Jul 2017 14:54: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 115877 invoked by uid 48); 11 Jul 2017 14:54:07 -0000 From: "msebor at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/81397] New: mistakes in .opt files not detected Date: Tue, 11 Jul 2017 14:54:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: bootstrap X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: msebor at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-07/txt/msg00936.txt.bz2 Content-length: 1505 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81397 Bug ID: 81397 Summary: mistakes in .opt files not detected Product: gcc Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: msebor at gcc dot gnu.org Target Milestone: --- As discussed in the thread below, the option processing scripts accept opti= on attributes with out-of-bounds or otherwise invalid parameters that are then rejected (or not processed correctly) at runtime, leading to subtle and not= so subtle bugs that are easy to miss if not exercised during testing. Even wh= en they are caught during testing, detecting and flagging them earlier in the process (i.e., when the script runs) would be better. An example of one such problem (discussed in the thread below) is the Init(value) attribute which requires that the open parenthesis not be separ= ated by a space from Init. If there is a space it's accepted but not handled correctly. Another example (also discussed there) is setting the initial value of an option in a LangEnabledBy() attribute to a value that's outside the range specified for the option by the IntegerRange() attribute. There are other, more subtle problems that can even lead to GCC crashing at runtime. Better error checking would also help prevent those. https://gcc.gnu.org/ml/gcc-patches/2017-07/msg00469.html >>From gcc-bugs-return-568386-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 15:11:57 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 61329 invoked by alias); 11 Jul 2017 15:11: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 57021 invoked by uid 48); 11 Jul 2017 15:11:52 -0000 From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/81391] [5/6/7 only] Use of parenthesis disables warning about incorrect size parameter Date: Tue, 11 Jul 2017 15:11:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 5.4.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 7.2 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: target_milestone short_desc 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: 2017-07/txt/msg00937.txt.bz2 Content-length: 568 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81391 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |7.2 Summary|Use of parenthesis disables |[5/6/7 only] Use of |warning about incorrect |parenthesis disables |size parameter |warning about incorrect | |size parameter >>From gcc-bugs-return-568387-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 15:14:46 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 74796 invoked by alias); 11 Jul 2017 15:14: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 69511 invoked by uid 48); 11 Jul 2017 15:14:42 -0000 From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81365] [7/8 Regression] GCC miscompiles swap Date: Tue, 11 Jul 2017 15:14:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: alias, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org X-Bugzilla-Target-Milestone: 7.2 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status assigned_to 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: 2017-07/txt/msg00938.txt.bz2 Content-length: 578 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81365 Jakub Jelinek changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gn= u.org --- Comment #5 from Jakub Jelinek --- Created attachment 41714 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D41714&action=3Dedit gcc8-pr81365.patch Untested fix. >>From gcc-bugs-return-568388-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 15:15:35 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 98073 invoked by alias); 11 Jul 2017 15:15:22 -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 85469 invoked by uid 48); 11 Jul 2017 15:15:01 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/81395] basic_filebuf::overflow recurses and overflows stack Date: Tue, 11 Jul 2017 15:15:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: 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: 2017-07/txt/msg00939.txt.bz2 Content-length: 1815 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81395 --- Comment #2 from Jonathan Wakely --- I'm testing this patch: --- a/libstdc++-v3/include/bits/fstream.tcc=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20 +++ b/libstdc++-v3/include/bits/fstream.tcc=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20 @@ -699,7 +699,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 if (__n =3D=3D 0)=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 {=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 - _M_set_buffer(0);=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20 + _M_set_buffer(-1);=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20 _M_reading =3D true;=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20 }=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 else if (__len =3D=3D 0) >>From gcc-bugs-return-568389-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 15:17:02 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 106260 invoked by alias); 11 Jul 2017 15:17:01 -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 101054 invoked by uid 48); 11 Jul 2017 15:16:56 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/81021] stack-use-after-scope false positive error with exceptions Date: Tue, 11 Jul 2017 15:17:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: marxin 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: 2017-07/txt/msg00940.txt.bz2 Content-length: 282 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81021 --- Comment #22 from Martin Li=C5=A1ka --- One more question, would it be possible to somehow attach gdb to the server which is tested? It will help me to debug where precisely is the stack poisoned? >>From gcc-bugs-return-568390-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 15:24:58 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 104405 invoked by alias); 11 Jul 2017 15:24: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 94168 invoked by uid 48); 11 Jul 2017 15:24:45 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/81021] stack-use-after-scope false positive error with exceptions Date: Tue, 11 Jul 2017 15:24:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: marxin 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: 2017-07/txt/msg00941.txt.bz2 Content-length: 648 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81021 --- Comment #23 from Martin Li=C5=A1ka --- (In reply to Martin Li=C5=A1ka from comment #22) > One more question, would it be possible to somehow attach gdb to the serv= er > which is tested? It will help me to debug where precisely is the stack > poisoned? Haha, can be done easily by: sleep_before_dying - Number of seconds to sleep between printing an error repo= rt and terminating the program. Useful for debugging purposes (e.g. when one n= eeds to attach gdb). I was just thinking of adding such option and look it already exists :) >>From gcc-bugs-return-568391-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 15:42:29 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 19731 invoked by alias); 11 Jul 2017 15:42:29 -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 17452 invoked by uid 48); 11 Jul 2017 15:42:23 -0000 From: "paolo.carlini at oracle dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/51270] missed warning about returning reference to temporary Date: Tue, 11 Jul 2017 15:42:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 4.6.2 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: paolo.carlini at oracle dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: 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: 2017-07/txt/msg00942.txt.bz2 Content-length: 549 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D51270 Paolo Carlini changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jwakely.gcc at gmail dot c= om, | |paolo.carlini at oracle do= t com --- Comment #10 from Paolo Carlini --- So, shall we add the testcase in Comment #7 and resolve this? Jon? >>From gcc-bugs-return-568392-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 15:52:36 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 129890 invoked by alias); 11 Jul 2017 15:52: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 127069 invoked by uid 48); 11 Jul 2017 15:52:31 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/81395] [5/6/7/8 Regression] basic_filebuf::overflow recurses and overflows stack Date: Tue, 11 Jul 2017 15:52:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: redi at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.5 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc cf_known_to_work assigned_to target_milestone 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: 2017-07/txt/msg00943.txt.bz2 Content-length: 1140 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81395 Jonathan Wakely changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |paolo.carlini at oracle do= t com Known to work| |4.5.4 Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu= .org Target Milestone|--- |5.5 Summary|basic_filebuf::overflow |[5/6/7/8 Regression] |recurses and overflows |basic_filebuf::overflow |stack |recurses and overflows | |stack Known to fail| |4.6.4, 4.7.4, 4.8.5, 4.9.4, | |5.4.0, 6.3.0, 7.0 --- Comment #3 from Jonathan Wakely --- This started in 4.6.0 with r87453 Paolo, does the change in comment 2 look right to you? >>From gcc-bugs-return-568393-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 15:56:28 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 76116 invoked by alias); 11 Jul 2017 15:56:28 -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 74005 invoked by uid 48); 11 Jul 2017 15:56:24 -0000 From: "paolo.carlini at oracle dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/81394] wrong "useless cast" message in inheriting constructor Date: Tue, 11 Jul 2017 15:56:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 6.3.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: paolo.carlini at oracle dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: 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: 2017-07/txt/msg00944.txt.bz2 Content-length: 516 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81394 Paolo Carlini changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Paolo Carlini --- Dup, already fixed. *** This bug has been marked as a duplicate of bug 70844 *** >>From gcc-bugs-return-568394-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 15:56:29 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 76497 invoked by alias); 11 Jul 2017 15:56:29 -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 74318 invoked by uid 48); 11 Jul 2017 15:56:24 -0000 From: "paolo.carlini at oracle dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/70844] [6/7/8 Regression] spurious -Wuseless-cast warning with inherited constructors Date: Tue, 11 Jul 2017 15:56:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 6.1.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: paolo.carlini at oracle dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jason at gcc dot gnu.org X-Bugzilla-Target-Milestone: 6.4 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: 2017-07/txt/msg00945.txt.bz2 Content-length: 452 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D70844 Paolo Carlini changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |f.heckenbach@fh-soft.de --- Comment #7 from Paolo Carlini --- *** Bug 81394 has been marked as a duplicate of this bug. *** >>From gcc-bugs-return-568395-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 15:57:24 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 102944 invoked by alias); 11 Jul 2017 15:57: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 100133 invoked by uid 48); 11 Jul 2017 15:57:20 -0000 From: "rdapp at linux dot vnet.ibm.com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/81362] [8.0 regression] FAIL: gcc.dg/vect/no-vfa-vect-57.c execution test Date: Tue, 11 Jul 2017 15:57:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: rdapp at linux dot vnet.ibm.com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: 2017-07/txt/msg00946.txt.bz2 Content-length: 625 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81362 --- Comment #6 from rdapp at linux dot vnet.ibm.com --- Created attachment 41715 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D41715&action=3Dedit Tentative patch Removed the npeel function argument, also removed body_cost_vec and the corresponding release ()es. I'm not so sure about the semantics of vecs in general. Are we leaking memory when not releasing the body_cost_vecs conta= ined in the various _vect_peel_extended_infos? If it was RAII-like body_cost_vec there would have been no need to release () body_cost_vec before, so I assu= me it is not. >>From gcc-bugs-return-568396-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 15:59:25 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 82052 invoked by alias); 11 Jul 2017 15:59:25 -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 79694 invoked by uid 48); 11 Jul 2017 15:59:21 -0000 From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81396] [7/8 Regression] Optimization of reading Little-Endian 64-bit number with portable code has a regression Date: Tue, 11 Jul 2017 15:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 7.2 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc target_milestone short_desc 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: 2017-07/txt/msg00947.txt.bz2 Content-length: 966 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81396 Jakub Jelinek changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-07-11 CC| |jakub at gcc dot gnu.org Target Milestone|--- |7.2 Summary|Optimization of reading |[7/8 Regression] |Little-Endian 64-bit number |Optimization of reading |with portable code has a |Little-Endian 64-bit number |regression |with portable code has a | |regression Ever confirmed|0 |1 --- Comment #1 from Jakub Jelinek --- Started with r239778. >>From gcc-bugs-return-568397-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 16:16:26 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 126218 invoked by alias); 11 Jul 2017 16:16: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 120018 invoked by uid 48); 11 Jul 2017 16:16:21 -0000 From: "paolo.carlini at oracle dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/81395] [5/6/7/8 Regression] basic_filebuf::overflow recurses and overflows stack Date: Tue, 11 Jul 2017 16:16:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: 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: redi at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.5 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: 2017-07/txt/msg00948.txt.bz2 Content-length: 635 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81395 --- Comment #4 from Paolo Carlini --- Seems weird: -1 means uncommitted (per the comment before _M_set_buffer) an= d we also set _M_reading? I don't think we do that anywhere else. But it's a long time... Note that I clearly remember somebody suggesting that in fact those _M_reading / _M_writing flags aren't necessary, we could in princinple do without, I even remember seeing a draft patch about that. Certainly, anyway= , if we think that uncomitted mode is fine here, there is a way to adjust (or le= ave alone) both not to cause problems... >>From gcc-bugs-return-568398-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 16:19:40 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 22280 invoked by alias); 11 Jul 2017 16:19: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 21037 invoked by uid 48); 11 Jul 2017 16:19:32 -0000 From: "krebbel at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug go/81393] Bootstrap failure on s390x-linux while building libgo against recent glibc Date: Tue, 11 Jul 2017 16:19:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: go X-Bugzilla-Version: 7.1.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: krebbel at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: krebbel at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed 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: 2017-07/txt/msg00949.txt.bz2 Content-length: 717 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81393 Andreas Krebbel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2017-07-11 Assignee|ian at airs dot com |krebbel at gcc dot = gnu.org Ever confirmed|0 |1 --- Comment #1 from Andreas Krebbel --- Created attachment 41716 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D41716&action=3Dedit Experimental patch The patch I'm currently testing >>From gcc-bugs-return-568399-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 16:42:35 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 91278 invoked by alias); 11 Jul 2017 16:42: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 84508 invoked by uid 48); 11 Jul 2017 16:42:30 -0000 From: "glisse at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81396] [7/8 Regression] Optimization of reading Little-Endian 64-bit number with portable code has a regression Date: Tue, 11 Jul 2017 16:42:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: glisse at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 7.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: 2017-07/txt/msg00950.txt.bz2 Content-length: 711 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81396 --- Comment #2 from Marc Glisse --- bswap was happy dealing with _2 =3D MEM[(const unsigned char *)&word]; _3 =3D (uint64_t) _2; _4 =3D MEM[(const unsigned char *)&word + 1B]; _5 =3D (uint64_t) _4; _6 =3D _5 << 8; _8 =3D MEM[(const unsigned char *)&word + 2B]; _9 =3D (uint64_t) _8; _10 =3D _9 << 16; _32 =3D _6 | _10; _11 =3D _3 | _32; etc, but has trouble with _21 =3D word_31(D) & 255; _1 =3D BIT_FIELD_REF ; _23 =3D (uint64_t) _1; _2 =3D _23 << 8; _4 =3D BIT_FIELD_REF ; _24 =3D (uint64_t) _4; _5 =3D _24 << 16; _32 =3D _2 | _5; _6 =3D _21 | _32; >>From gcc-bugs-return-568400-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 16:42:48 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 101612 invoked by alias); 11 Jul 2017 16:42: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 96903 invoked by uid 48); 11 Jul 2017 16:42:43 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/51270] missed warning about returning reference to temporary Date: Tue, 11 Jul 2017 16:42:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 4.6.2 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: 2017-07/txt/msg00951.txt.bz2 Content-length: 213 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D51270 --- Comment #11 from Jonathan Wakely --- It's a pity you need at least -O2 for the warnings, but I agree we can clos= e it as fixed. >>From gcc-bugs-return-568401-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 16:46:22 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 63980 invoked by alias); 11 Jul 2017 16:46:22 -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 62303 invoked by uid 48); 11 Jul 2017 16:46:17 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/81021] stack-use-after-scope false positive error with exceptions Date: Tue, 11 Jul 2017 16:46:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: marxin 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: 2017-07/txt/msg00952.txt.bz2 Content-length: 989 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81021 --- Comment #24 from Martin Li=C5=A1ka --- Just run with current trunk and it works (it fails after a minute in =3D=3D13736=3D=3DERROR: AddressSanitizer: stack-overflow on address 0x2adb9= b406e48 (pc 0x0000067d8638 bp 0x2adb9b408020 sp 0x2adb9b406e30 T1) So I'm going to test gcc-7-branch and I hope this patch is missing: commit 5b64e274ea8c9aaedcebc1d6ad285a11e64ab086 Author: marxin Date: Fri Jun 30 08:51:00 2017 +0000 Call BUILT_IN_ASAN_HANDLE_NO_RETURN before BUILT_IN_UNWIND_RESUME (PR sanitizer/81021). 2017-06-30 Martin Liska PR sanitizer/81021 * g++.dg/asan/pr81021.C: New test. 2017-06-30 Martin Liska PR sanitizer/81021 * tree-eh.c (lower_resx): Call BUILT_IN_ASAN_HANDLE_NO_RETURN before BUILT_IN_UNWIND_RESUME when ASAN is used. >>From gcc-bugs-return-568402-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 16:46:53 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 86306 invoked by alias); 11 Jul 2017 16:46:53 -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 81673 invoked by uid 48); 11 Jul 2017 16:46:48 -0000 From: "krebbel at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug go/81393] Bootstrap failure on s390x-linux while building libgo against recent glibc Date: Tue, 11 Jul 2017 16:46:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: go X-Bugzilla-Version: 7.1.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: krebbel at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: krebbel at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.isobsolete 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: 2017-07/txt/msg00953.txt.bz2 Content-length: 575 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81393 Andreas Krebbel changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #41716|0 |1 is obsolete| | --- Comment #2 from Andreas Krebbel --- Created attachment 41717 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D41717&action=3Dedit Tested Patch I had to add typecasts also for the 64 bit code. >>From gcc-bugs-return-568403-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 16:48:54 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 87809 invoked by alias); 11 Jul 2017 16:48: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 83252 invoked by uid 48); 11 Jul 2017 16:48:48 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/81395] [5/6/7/8 Regression] basic_filebuf::overflow recurses and overflows stack Date: Tue, 11 Jul 2017 16:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: redi at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.5 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: 2017-07/txt/msg00954.txt.bz2 Content-length: 590 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81395 --- Comment #5 from Jonathan Wakely --- PR 45708 suggested that _M_reading and _M_writing aren't needed. I haven't found a patch to implement that, but I haven't looked too hard. You make a good point that going into uncommitted mode with _M_reading =3D= =3D true isn't done elsewhere. I don't understand the state machine, so I'm very uns= ure about changing anything here. But _M_set_buffer(0) seems wrong, since that causes an unwanted(?) call to this->setp(_M_buf, _M_buf + _M_buf_size - 1); from xsgetn. >>From gcc-bugs-return-568404-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 16:55:05 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 69776 invoked by alias); 11 Jul 2017 16:55:05 -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 69735 invoked by uid 48); 11 Jul 2017 16:55:01 -0000 From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81396] [7/8 Regression] Optimization of reading Little-Endian 64-bit number with portable code has a regression Date: Tue, 11 Jul 2017 16:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 7.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: 2017-07/txt/msg00955.txt.bz2 Content-length: 154 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81396 --- Comment #3 from Jakub Jelinek --- I'll have a look at that tomorrow. >>From gcc-bugs-return-568405-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 16:57:03 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 77512 invoked by alias); 11 Jul 2017 16:57: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 76939 invoked by uid 48); 11 Jul 2017 16:56:57 -0000 From: "paolo.carlini at oracle dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/81395] [5/6/7/8 Regression] basic_filebuf::overflow recurses and overflows stack Date: Tue, 11 Jul 2017 16:57:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: 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: redi at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.5 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: 2017-07/txt/msg00956.txt.bz2 Content-length: 376 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81395 --- Comment #6 from Paolo Carlini --- The relevant xsgetn code essentially is an optimization, right? Shouldn't be too difficult to figure out what would happen in the slow, correct case... What's wrong with a normal uncommitted case, thus _M_reading =3D false? Performance? Correctness? >>From gcc-bugs-return-568406-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 16:58:04 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 80864 invoked by alias); 11 Jul 2017 16:58:04 -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 80723 invoked by uid 48); 11 Jul 2017 16:57:59 -0000 From: "paolo.carlini at oracle dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/51270] missed warning about returning reference to temporary Date: Tue, 11 Jul 2017 16:58:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 4.6.2 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: paolo.carlini at oracle dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: 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: 2017-07/txt/msg00957.txt.bz2 Content-length: 191 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D51270 --- Comment #12 from Paolo Carlini --- Certainly a pity, but I think it's a rather well known issue... >>From gcc-bugs-return-568407-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 17:08:34 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 92899 invoked by alias); 11 Jul 2017 17:08: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 81239 invoked by uid 48); 11 Jul 2017 17:08:28 -0000 From: "segher at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/81317] builtin_vec_ld fails for powerpc with altivec Date: Tue, 11 Jul 2017 17:08:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: segher at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: segher at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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: 2017-07/txt/msg00958.txt.bz2 Content-length: 560 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81317 Segher Boessenkool changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |segher at gcc dot g= nu.org --- Comment #9 from Segher Boessenkool --- Created attachment 41718 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D41718&action=3Dedit proposed patch Hi Randy, Could you test this patch please? >>From gcc-bugs-return-568408-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 17:11:39 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 25790 invoked by alias); 11 Jul 2017 17:11: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 25624 invoked by uid 48); 11 Jul 2017 17:11:32 -0000 From: "segher at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/81317] builtin_vec_ld fails for powerpc with altivec Date: Tue, 11 Jul 2017 17:11:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: segher at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: segher at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.isobsolete 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: 2017-07/txt/msg00959.txt.bz2 Content-length: 578 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81317 Segher Boessenkool changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #41718|0 |1 is obsolete| | --- Comment #10 from Segher Boessenkool --- Created attachment 41719 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D41719&action=3Dedit proposed patch Again, but without whitespace damage. Sigh. >>From gcc-bugs-return-568409-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 17:23:29 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 42894 invoked by alias); 11 Jul 2017 17:23:29 -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 40733 invoked by uid 48); 11 Jul 2017 17:23:24 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/81395] [5/6/7/8 Regression] basic_filebuf::overflow recurses and overflows stack Date: Tue, 11 Jul 2017 17:23:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: redi at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.5 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: 2017-07/txt/msg00960.txt.bz2 Content-length: 1148 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81395 --- Comment #7 from Jonathan Wakely --- (In reply to Jonathan Wakely from comment #3) > This started in 4.6.0 with r87453 It did start with 4.6.0 but that commit was already in 4.5.4 so it can't ha= ve been that one. It seems to be the change to overflow in r164529 i.e. the fix for PR 45628, which did this to basic_filebuf::overflow, introducing the potential recursion: @@ -410,8 +426,16 @@ int_type __ret =3D traits_type::eof(); const bool __testeof =3D traits_type::eq_int_type(__c, __ret); const bool __testout =3D _M_mode & ios_base::out; - if (__testout && !_M_reading) + if (__testout) { + if (_M_reading) + { + _M_destroy_pback(); + const int __gptr_off =3D _M_get_ext_pos(_M_state_last); + if (_M_seek(__gptr_off, ios_base::cur, _M_state_last) + =3D=3D pos_type(off_type(-1))) + return __ret; + } if (this->pbase() < this->pptr()) { // If appropriate, append the overflow char. >>From gcc-bugs-return-568410-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 17:28:06 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 26973 invoked by alias); 11 Jul 2017 17:28:05 -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 25257 invoked by uid 48); 11 Jul 2017 17:28:02 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/81395] [5/6/7/8 Regression] basic_filebuf::overflow recurses and overflows stack Date: Tue, 11 Jul 2017 17:28:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: redi at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.5 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: 2017-07/txt/msg00961.txt.bz2 Content-length: 448 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81395 --- Comment #8 from Jonathan Wakely --- (In reply to Paolo Carlini from comment #6) > The relevant xsgetn code essentially is an optimization, right? Shouldn't= be > too difficult to figure out what would happen in the slow, correct case... > What's wrong with a normal uncommitted case, thus _M_reading =3D false? > Performance? Correctness? I have **no** idea :-) >>From gcc-bugs-return-568411-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 18:11:26 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 116670 invoked by alias); 11 Jul 2017 18:11:25 -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 116567 invoked by uid 48); 11 Jul 2017 18:11:21 -0000 From: "schwab@linux-m68k.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/81362] [8.0 regression] FAIL: gcc.dg/vect/no-vfa-vect-57.c execution test Date: Tue, 11 Jul 2017 18:11:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: wrong-code 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: 2017-07/txt/msg00962.txt.bz2 Content-length: 190 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81362 --- Comment #7 from Andreas Schwab --- This fixes both no-vfa-vect-57.c and no-vfa-vect-61.c for -m64 and -m32. >>From gcc-bugs-return-568412-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 18:23:57 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 4034 invoked by alias); 11 Jul 2017 18:23: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 3933 invoked by uid 48); 11 Jul 2017 18:23:53 -0000 From: "asolokha at gmx dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/70992] Infinite recursion between fold_build2_stat_loc and fold_binary_loc w/ -fwrapv Date: Tue, 11 Jul 2017 18:23:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 6.1.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: asolokha at gmx dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: 2017-07/txt/msg00963.txt.bz2 Content-length: 706 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D70992 Arseny Solokha changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail| |8.0 --- Comment #4 from Arseny Solokha --- The following makes gcc-8.0.0-alpha20170709 snapshot ICE w/ no command line options at all: typedef unsigned int uint32_t; uint32_t ls (uint32_t so) { return (so + so) * (0x80000000 / 0 + 1); } % gcc-8.0.0-alpha20170709 -c -w sxijy9dr.c x86_64-unknown-linux-gnu-gcc-8.0.0-alpha20170709: internal compiler error: Segmentation fault (program cc1) >>From gcc-bugs-return-568413-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 18:31:19 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 38318 invoked by alias); 11 Jul 2017 18:31: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 38256 invoked by uid 48); 11 Jul 2017 18:31:14 -0000 From: "segher at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/81317] builtin_vec_ld fails for powerpc with altivec Date: Tue, 11 Jul 2017 18:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: segher at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: segher 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: 2017-07/txt/msg00964.txt.bz2 Content-length: 1511 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81317 --- Comment #11 from Segher Boessenkool --- The original testcase still ICEs ("smaller reproducer" I never got to fail). (trunk, no options whatsoever): 81317-1.c: In function 'jsimd_ycc_rgb_convert_altivec': 81317-1.c:184:6: internal compiler error: Segmentation fault void jsimd_ycc_rgb_convert_altivec (JDIMENSION out_width, JSAMPIMAGE input_buf, ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 0x108f8edb crash_signal /home/segher/src/gcc/gcc/toplev.c:338 0x1093ed98 contains_struct_check(tree_node*, tree_node_structure_enum, char const*, int, char const*) /home/segher/src/gcc/gcc/tree.h:3196 0x1093ed98 verify_gimple_assign_binary /home/segher/src/gcc/gcc/tree-cfg.c:3828 0x10946927 verify_gimple_in_seq_2 /home/segher/src/gcc/gcc/tree-cfg.c:4936 0x1094c0ef verify_gimple_in_seq(gimple*) /home/segher/src/gcc/gcc/tree-cfg.c:4975 0x105af4a7 gimplify_body(tree_node*, bool) /home/segher/src/gcc/gcc/gimplify.c:12589 0x105af91f gimplify_function_tree(tree_node*) /home/segher/src/gcc/gcc/gimplify.c:12679 0x1039d487 cgraph_node::analyze() /home/segher/src/gcc/gcc/cgraphunit.c:668 0x103a11d7 analyze_functions /home/segher/src/gcc/gcc/cgraphunit.c:1129 0x103a298f symbol_table::finalize_compilation_unit() /home/segher/src/gcc/gcc/cgraphunit.c:2607 __builtin_altivec_vsubuhm (cbh, pw_cj); is transformed to =3D cbh - pw_cj; and that blows up. >>From gcc-bugs-return-568414-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 18:36:53 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 59952 invoked by alias); 11 Jul 2017 18:36:53 -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 59562 invoked by uid 48); 11 Jul 2017 18:36:47 -0000 From: "dmalcolm at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/81269] wrong color highlighting in -Wrestrict warnings Date: Tue, 11 Jul 2017 18:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 7.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: dmalcolm at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: 2017-07/txt/msg00965.txt.bz2 Content-length: 836 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81269 David Malcolm changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dmalcolm at gcc dot gnu.org --- Comment #2 from David Malcolm --- As noted in https://gcc.gnu.org/ml/gcc-patches/2017-07/msg00548.html, which describes why those colors were picked, this is "working as intended"... ...but I'm having second thoughts about how sane my intentions were when I implemented this colorization system - it seems garish to me now. I think I now favor emulating what clang does, which is to *not* color the printed source lines, and to use just one color (green) for underlines and carets. >>From gcc-bugs-return-568415-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 18:39:09 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 66169 invoked by alias); 11 Jul 2017 18:39:08 -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 66096 invoked by uid 48); 11 Jul 2017 18:39:03 -0000 From: "seurer at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/81399] New: New test case 27_io/basic_stringstream/assign/81338.cc fails on powerpc64le Date: Tue, 11 Jul 2017 18:39:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: testsuite X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: seurer at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-07/txt/msg00966.txt.bz2 Content-length: 3401 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81399 Bug ID: 81399 Summary: New test case 27_io/basic_stringstream/assign/81338.cc fails on powerpc64le Product: gcc Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsuite Assignee: unassigned at gcc dot gnu.org Reporter: seurer at gcc dot gnu.org Target Milestone: --- 27_io/basic_stringstream/assign/81338.cc fails on powerpc64 LE. It works fi= ne on BE. seurer@genoa:~/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/libstdc++-v= 3/testsuite$ make -k check RUNTESTFLAGS=3Dconformance.exp=3D27_io/basic_stringstream/assign/81338.cc . . . spawn /home/seurer/gcc/build/gcc-test/./gcc/xg++ -shared-libgcc -B/home/seurer/gcc/build/gcc-test/./gcc -nostdinc++ -L/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/libstdc++-v= 3/src -L/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/libstdc++-v= 3/src/.libs -L/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/libstdc++-v= 3/libsupc++/.libs -B/home/seurer/gcc/install/gcc-test/powerpc64le-unknown-linux-gnu/bin/ -B/home/seurer/gcc/install/gcc-test/powerpc64le-unknown-linux-gnu/lib/ -isy= stem /home/seurer/gcc/install/gcc-test/powerpc64le-unknown-linux-gnu/include -isystem /home/seurer/gcc/install/gcc-test/powerpc64le-unknown-linux-gnu/sys-include -B/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libstdc++= -v3/src/.libs -fmessage-length=3D0 -fno-show-column -ffunction-sections -fdata-sections -= g -O2 -DLOCALEDIR=3D"." -nostdinc++ -I/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/libstdc++-v= 3/include/powerpc64le-unknown-linux-gnu -I/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/libstdc++-v= 3/include -I/home/seurer/gcc/gcc-test/libstdc++-v3/libsupc++ -I/home/seurer/gcc/gcc-test/libstdc++-v3/include/backward -I/home/seurer/gcc/gcc-test/libstdc++-v3/testsuite/util /home/seurer/gcc/gcc-test/libstdc++-v3/testsuite/27_io/basic_stringstream/a= ssign/81338.cc -include bits/stdc++.h -fno-diagnostics-show-caret -fdiagnostics-color=3Dne= ver ./libtestc++.a -Wl,--gc-sections -L/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/libstdc++-v= 3/src/filesystem/.libs -lm -o ./81338.exe PASS: 27_io/basic_stringstream/assign/81338.cc (test for excess errors) Setting LD_LIBRARY_PATH to :/home/seurer/gcc/build/gcc-test/gcc:/home/seurer/gcc/build/gcc-test/powerp= c64le-unknown-linux-gnu/./libstdc++-v3/../libgomp/.libs:/home/seurer/gcc/bu= ild/gcc-test/powerpc64le-unknown-linux-gnu/./libstdc++-v3/src/.libs::/home/= seurer/gcc/build/gcc-test/gcc:/home/seurer/gcc/build/gcc-test/powerpc64le-u= nknown-linux-gnu/./libstdc++-v3/../libgomp/.libs:/home/seurer/gcc/build/gcc= -test/powerpc64le-unknown-linux-gnu/./libstdc++-v3/src/.libs:/home/seurer/g= cc/install/gcc-7.1.0/lib64 spawn [open ...] /home/seurer/gcc/gcc-test/libstdc++-v3/testsuite/27_io/basic_stringstream/a= ssign/81338.cc:30: void test01(): Assertion 'static_cast(ss)' failed. FAIL: 27_io/basic_stringstream/assign/81338.cc execution test testcase /home/seurer/gcc/gcc-test/libstdc++-v3/testsuite/libstdc++-dg/conformance.e= xp completed in 15 seconds =3D=3D=3D libstdc++ Summary =3D=3D=3D # of expected passes 1 # of unexpected failures 1 >>From gcc-bugs-return-568416-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 18:40:07 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 69040 invoked by alias); 11 Jul 2017 18:40: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 68857 invoked by uid 48); 11 Jul 2017 18:40:03 -0000 From: "wschmidt at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/81317] builtin_vec_ld fails for powerpc with altivec Date: Tue, 11 Jul 2017 18:40:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: wschmidt at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: segher at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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: 2017-07/txt/msg00967.txt.bz2 Content-length: 775 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81317 Bill Schmidt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wschmidt at gcc dot gnu.org --- Comment #12 from Bill Schmidt --- (In reply to Segher Boessenkool from comment #11) >=20 > __builtin_altivec_vsubuhm (cbh, pw_cj); >=20 >=20 > is transformed to >=20 >=20 > =3D cbh - pw_cj; >=20 >=20 > and that blows up. Yeah, well...the original source is obviously wrong, since __builtin_altivec_vsubuhm produces a result that is thrown away. We should avoid optimizing in this situation, but it's an ice-on-invalid. >>From gcc-bugs-return-568417-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 18:41:36 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 80475 invoked by alias); 11 Jul 2017 18:41: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 79154 invoked by uid 48); 11 Jul 2017 18:41:31 -0000 From: "wschmidt at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/81317] builtin_vec_ld fails for powerpc with altivec Date: Tue, 11 Jul 2017 18:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: wschmidt at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: segher at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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: 2017-07/txt/msg00968.txt.bz2 Content-length: 481 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81317 Bill Schmidt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |willschm at gcc dot gnu.org --- Comment #13 from Bill Schmidt --- CCing Will Schmidt for the general gimple-folding issue of built-in calls w= ith missing LHSes. >>From gcc-bugs-return-568418-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 19:03:22 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 114891 invoked by alias); 11 Jul 2017 19:03:22 -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 114839 invoked by uid 48); 11 Jul 2017 19:03:18 -0000 From: "gccbugzilla.severach at spamgourmet dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/81400] New: Stack smashing not caught by stack protector strong and allowing me to stack smash Date: Tue, 11 Jul 2017 19:03:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 7.1.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gccbugzilla.severach at spamgourmet dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-07/txt/msg00969.txt.bz2 Content-length: 1140 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81400 Bug ID: 81400 Summary: Stack smashing not caught by stack protector strong and allowing me to stack smash Product: gcc Version: 7.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: gccbugzilla.severach at spamgourmet dot com Target Milestone: --- Created attachment 41720 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D41720&action=3Dedit Stack smash demo I've made up some simple cases where stack smashing is not being caught. In= one case -fstack-protector-strong prevents a seg fault and allows me to stack s= mash unchallenged. The demo is attached as a .tgz. Though this is against the rules the bug sy= stem doesn't allow me to submit the multiple files requested any other way. Cons= ider this a bug report that the bug writing guidelines should be changed to "we require a .tar .tgz .zip of the files to be submitted" or the bug tracker n= eeds to accept multiple files. >>From gcc-bugs-return-568419-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 19:18:19 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 40465 invoked by alias); 11 Jul 2017 19:18: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 Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 40394 invoked by uid 48); 11 Jul 2017 19:18:15 -0000 From: "andrewjcg at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/71850] @file should be used to cc1/cc1plus when @file is used Date: Tue, 11 Jul 2017 19:18:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: driver X-Bugzilla-Version: 6.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: andrewjcg at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: 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: 2017-07/txt/msg00970.txt.bz2 Content-length: 763 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D71850 Andrew Gallagher changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrewjcg at gmail dot com --- Comment #5 from Andrew Gallagher --- I'm interesting in attempting to fix this, but first wanted some guidance on where to look. After an initial skim, what about modifying the `execute` function to always serialize `command[n].argv` to an @file when executing t= he command if `at_file_supplied`? The main downside I see here is that it ass= umes all subcommands support @file syntax when the frontend does. >>From gcc-bugs-return-568420-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 19:50:17 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 61557 invoked by alias); 11 Jul 2017 19:50: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 61453 invoked by uid 48); 11 Jul 2017 19:50:12 -0000 From: "meissner at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/81193] PowerPC GCC __builtin_cpu_is and __builtin_cpu_supports should warn about old libraries Date: Tue, 11 Jul 2017 19:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: meissner at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: meissner at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: 2017-07/txt/msg00971.txt.bz2 Content-length: 260 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81193 --- Comment #12 from Michael Meissner --- Created attachment 41721 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D41721&action=3Dedit Proposed patch to fix the problem >>From gcc-bugs-return-568421-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 20:53:36 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 35534 invoked by alias); 11 Jul 2017 20:53: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 35480 invoked by uid 48); 11 Jul 2017 20:53:32 -0000 From: "seurer at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/81399] New test case 27_io/basic_stringstream/assign/81338.cc fails on powerpc64le Date: Tue, 11 Jul 2017 20:53:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: testsuite X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: seurer at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: 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: 2017-07/txt/msg00972.txt.bz2 Content-length: 173 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81399 --- Comment #1 from seurer at gcc dot gnu.org --- I was wrong, it fails at least some of the time on powerpc64 BE too. >>From gcc-bugs-return-568422-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 21:21:23 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 3382 invoked by alias); 11 Jul 2017 21:21: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 2567 invoked by uid 48); 11 Jul 2017 21:21:15 -0000 From: "segher at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/81317] builtin_vec_ld fails for powerpc with altivec Date: Tue, 11 Jul 2017 21:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: segher at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: segher 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: 2017-07/txt/msg00973.txt.bz2 Content-length: 310 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81317 --- Comment #14 from Segher Boessenkool --- Created attachment 41722 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D41722&action=3Dedit second patch, for the original problem This one should solve the original problem. >>From gcc-bugs-return-568423-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 21:21:39 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 4859 invoked by alias); 11 Jul 2017 21:21: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 4151 invoked by uid 48); 11 Jul 2017 21:21:32 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/81399] New test case 27_io/basic_stringstream/assign/81338.cc fails on powerpc64le Date: Tue, 11 Jul 2017 21:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: testsuite X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: 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: 2017-07/txt/msg00974.txt.bz2 Content-length: 166 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81399 --- Comment #2 from Jonathan Wakely --- FWIW it passes on gcc112 in the compile farm. >>From gcc-bugs-return-568425-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 21:25:50 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 16241 invoked by alias); 11 Jul 2017 21:25: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 15901 invoked by uid 55); 11 Jul 2017 21:25:38 -0000 From: "paolo at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/51270] missed warning about returning reference to temporary Date: Tue, 11 Jul 2017 21:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 4.6.2 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: paolo at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: 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: 2017-07/txt/msg00976.txt.bz2 Content-length: 509 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D51270 --- Comment #13 from paolo at gcc dot gnu.org --- Author: paolo Date: Tue Jul 11 21:24:11 2017 New Revision: 250140 URL: https://gcc.gnu.org/viewcvs?rev=3D250140&root=3Dgcc&view=3Drev Log: 2017-07-11 Paolo Carlini PR c++/51270 * g++.dg/warn/Wreturn-local-addr-3.C: New. Added: trunk/gcc/testsuite/g++.dg/warn/Wreturn-local-addr-3.C Modified: trunk/gcc/testsuite/ChangeLog >>From gcc-bugs-return-568424-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 21:25:49 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 16110 invoked by alias); 11 Jul 2017 21:25:49 -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 15868 invoked by uid 48); 11 Jul 2017 21:25:36 -0000 From: "babokin at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/81387] UBSAN consumes too much memory at -O2 Date: Tue, 11 Jul 2017 21:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: babokin 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: 2017-07/txt/msg00975.txt.bz2 Content-length: 1067 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81387 --- Comment #3 from Dmitry Babokin --- Interesting that you've mentioned -fno-sanitize-recover, I haven't realized that it has effect on the number of basic blocks. But by default I run "-fsanitize=3Dundefined -fno-sanitize-recover=3Dundefined", so the numbers = that I posted are for this combination (-fno-sanitize-recover=3Dall is effectively= the same). I've tried without -fno-sanitize-recover=3Dundefined and it is: -O2 -fsanitize=3Dundefined: 358s, 62Gb -O1 -fsanitize=3Dundefined: 280s, 2.7Gb Also clang trunk: -O2 -fsanitize=3Dundefined: 173s, 1.5Gb -O2 -fsanitize=3Dundefined -fno-sanitize-recover=3Dundefined: 224s, 1.8Gb I understand that the reasons for consuming more memory with UBSAN enabled = are quite fundamental, but looking at such an extreme increase may uncover prob= lems when algorithms consume more that they supposed to. Again, I'm not insisting on fixing it, I'm rather drawing attention to suspicious behaviour, which you may consider worth looking at. >>From gcc-bugs-return-568426-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 21:26:37 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 18098 invoked by alias); 11 Jul 2017 21:26: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 17998 invoked by uid 48); 11 Jul 2017 21:26:31 -0000 From: "paolo.carlini at oracle dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/51270] missed warning about returning reference to temporary Date: Tue, 11 Jul 2017 21:26:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 4.6.2 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: paolo.carlini at oracle dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution 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: 2017-07/txt/msg00977.txt.bz2 Content-length: 499 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D51270 Paolo Carlini changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Target Milestone|--- |5.0 --- Comment #14 from Paolo Carlini --- Closing, then. >>From gcc-bugs-return-568427-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 21:30:48 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 22881 invoked by alias); 11 Jul 2017 21:30: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 22774 invoked by uid 48); 11 Jul 2017 21:30:43 -0000 From: "segher at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/81317] builtin_vec_ld fails for powerpc with altivec Date: Tue, 11 Jul 2017 21:30:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: segher at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: segher at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.isobsolete 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: 2017-07/txt/msg00978.txt.bz2 Content-length: 585 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81317 Segher Boessenkool changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #41722|0 |1 is obsolete| | --- Comment #15 from Segher Boessenkool --- Created attachment 41723 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D41723&action=3Dedit patch for the orig problem I hate clicky interfaces. Ugh. Sorry. >>From gcc-bugs-return-568429-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 21:35:58 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 29130 invoked by alias); 11 Jul 2017 21:35: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 29024 invoked by uid 48); 11 Jul 2017 21:35:52 -0000 From: "anatol.pomozov at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/81342] LTO: lto1: internal compiler error: Segmentation fault Date: Tue, 11 Jul 2017 21:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: lto X-Bugzilla-Severity: normal X-Bugzilla-Who: anatol.pomozov at gmail dot com X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: 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: 2017-07/txt/msg00980.txt.bz2 Content-length: 625 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81342 --- Comment #3 from Anatol --- Hi I indeed observe the issue in a kernel project. It is a custom x86 kernel t= hat is not published yet. I tried to narrow down use case and I think I found how to reproduce the is= sue easily. It looks like a trigger pattern is: 1) compile one file as 32bit code (-m32) 2) convert it to 64bit elf object using objcopy 3) link the object above with regular 64bit elf If "-flto" is not used then linking works fine otherwise I have the crash above. Here is an attached repo case for your convenience. >>From gcc-bugs-return-568428-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 21:35:31 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 28185 invoked by alias); 11 Jul 2017 21:35: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 28127 invoked by uid 48); 11 Jul 2017 21:35:26 -0000 From: "anatol.pomozov at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/81342] LTO: lto1: internal compiler error: Segmentation fault Date: Tue, 11 Jul 2017 21:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: lto X-Bugzilla-Severity: normal X-Bugzilla-Who: anatol.pomozov at gmail dot com X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created Message-ID: 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: 2017-07/txt/msg00979.txt.bz2 Content-length: 247 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81342 --- Comment #2 from Anatol --- Created attachment 41724 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D41724&action=3Dedit Reproduce lto crash with LD >>From gcc-bugs-return-568430-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 21:47:09 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 62410 invoked by alias); 11 Jul 2017 21:47: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 62312 invoked by uid 48); 11 Jul 2017 21:47:01 -0000 From: "catwell-gcc at catwell dot info" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/81401] New: False positive sprintf warning at O2 (-Wformat-overflow) Date: Tue, 11 Jul 2017 21:47:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 7.1.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: catwell-gcc at catwell dot info X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-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: 2017-07/txt/msg00981.txt.bz2 Content-length: 2288 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81401 Bug ID: 81401 Summary: False positive sprintf warning at O2 (-Wformat-overflow) Product: gcc Version: 7.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: catwell-gcc at catwell dot info Target Milestone: --- Using GCC 7.1.1, with: #include int main () { int i; char obuf[3]; int start =3D 0x00; for (i =3D start; i <=3D 0xff; ++i) { sprintf(obuf, "%02x", i); } return 0; } I get: demo.c: In function =E2=80=98main=E2=80=99: demo.c:6:23: warning: =E2=80=98sprintf=E2=80=99 may write a terminating nul= past the end of the destination [-Wformat-overflow=3D] sprintf(obuf, "%02x", i); ^~~~~~ demo.c:6:9: note: =E2=80=98sprintf=E2=80=99 output between 3 and 4 bytes in= to a destination of size 3 sprintf(obuf, "%02x", i); ^~~~~~~~~~~~~~~~~~~~~~~~ At O1 I don't get the warning. If I set `start` to `0xfb` or `0xfc`, I get the same warning. If I set it to `0xfe` or `0xff` I don't get a warning. If I set it to `0xfd` I get the war= ning *twice*: demo.c: In function =E2=80=98main=E2=80=99: demo.c:6:23: warning: =E2=80=98sprintf=E2=80=99 may write a terminating nul= past the end of the destination [-Wformat-overflow=3D] sprintf(obuf, "%02x", i); ^~~~~~ demo.c:6:9: note: =E2=80=98sprintf=E2=80=99 output between 3 and 4 bytes in= to a destination of size 3 sprintf(obuf, "%02x", i); ^~~~~~~~~~~~~~~~~~~~~~~~ demo.c:6:23: warning: =E2=80=98sprintf=E2=80=99 may write a terminating nul= past the end of the destination [-Wformat-overflow=3D] sprintf(obuf, "%02x", i); ^~~~~~ demo.c:6:9: note: =E2=80=98sprintf=E2=80=99 output between 3 and 4 bytes in= to a destination of size 3 sprintf(obuf, "%02x", i); ^~~~~~~~~~~~~~~~~~~~~~~~ I was advised to open a new bug for this at [1] even though it looks simila= r to [2]. [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D79257#c8 [2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D78969#c4 >>From gcc-bugs-return-568431-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 21:48:54 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 64364 invoked by alias); 11 Jul 2017 21:48: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 64223 invoked by uid 48); 11 Jul 2017 21:48:47 -0000 From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81401] False positive sprintf warning at O2 (-Wformat-overflow) Date: Tue, 11 Jul 2017 21:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 7.1.1 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: component 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: 2017-07/txt/msg00982.txt.bz2 Content-length: 437 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81401 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- Component|c |tree-optimization --- Comment #1 from Andrew Pinski --- It is an off by one issue with how loop bounds are calculated. >>From gcc-bugs-return-568432-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 22:18:58 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 24953 invoked by alias); 11 Jul 2017 22:18: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 24912 invoked by uid 48); 11 Jul 2017 22:18:54 -0000 From: "msebor at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/81402] New: unhelpful -Wparentheses suggestion for assignment from non-zero constant Date: Tue, 11 Jul 2017 22:18:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: trivial X-Bugzilla-Who: msebor at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-07/txt/msg00983.txt.bz2 Content-length: 1644 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81402 Bug ID: 81402 Summary: unhelpful -Wparentheses suggestion for assignment from non-zero constant Product: gcc Version: 8.0 Status: UNCONFIRMED Severity: trivial Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: msebor at gcc dot gnu.org Target Milestone: --- In response to a controlling expression in an if statement that is an assignment expression, -Wparentheses suggests to enclose the expression in parentheses. That suggestion is only helpful in cases where the value of r= ight operand of the assignment is unknown. Otherwise, when its value is constan= t, and especially when the operand is a literal, the assignment is almost certainly wrong because testing the value of a constant for equality to zer= o is pointless. In those cases, pointing out the likely mistake rather than suggesting to use parentheses would be more helpful. $ cat a.c && gcc -S -Wall a.c oid f (int i, int j) { if (i =3D j) { } // assignment could be intended } void g (int i) { if (i =3D 1) { } // assignment almost certainly not intended } a.c: In function =E2=80=98f=E2=80=99: a.c:3:7: warning: suggest parentheses around assignment used as truth value [-Wparentheses] if (i =3D j) { } // assignment could be intended ^ a.c: In function =E2=80=98g=E2=80=99: a.c:8:7: warning: suggest parentheses around assignment used as truth value [-Wparentheses] if (i =3D 1) { } // assignment almost certainly not intended ^ >>From gcc-bugs-return-568433-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 22:23:26 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 12573 invoked by alias); 11 Jul 2017 22:23: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 12500 invoked by uid 48); 11 Jul 2017 22:23:20 -0000 From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/81402] unhelpful -Wparentheses suggestion for assignment from non-zero constant Date: Tue, 11 Jul 2017 22:23:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: trivial X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: 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: 2017-07/txt/msg00984.txt.bz2 Content-length: 575 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81402 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Andrew Pinski --- I disagree. In fact this warning has saved me many times. I had accidentally wrote: if (a =3D f()) and I was like why I was getting incorrect results. >>From gcc-bugs-return-568434-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 22:23:31 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 13112 invoked by alias); 11 Jul 2017 22:23: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 12633 invoked by uid 48); 11 Jul 2017 22:23:26 -0000 From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/81402] unhelpful -Wparentheses suggestion for assignment from non-zero constant Date: Tue, 11 Jul 2017 22:23:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: trivial X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WONTFIX X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: 2017-07/txt/msg00985.txt.bz2 Content-length: 519 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81402 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |WONTFIX --- Comment #2 from Andrew Pinski --- I disagree. In fact this warning has saved me many times. I had accidentally wrote: if (a =3D f()) and I was like why I was getting incorrect results. >>From gcc-bugs-return-568435-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 22:25:46 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 17576 invoked by alias); 11 Jul 2017 22:25: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 17532 invoked by uid 48); 11 Jul 2017 22:25:42 -0000 From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/81402] unhelpful -Wparentheses suggestion for assignment from non-zero constant Date: Tue, 11 Jul 2017 22:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: enhancement X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: keywords bug_status resolution bug_severity 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: 2017-07/txt/msg00986.txt.bz2 Content-length: 803 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81402 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |diagnostic Status|RESOLVED |UNCONFIRMED Resolution|WONTFIX |--- Severity|trivial |enhancement --- Comment #3 from Andrew Pinski --- Wait I read you suggestion incorrectly. You want to suggest that maybe you wanted to use =3D=3D instead here? I think that is wrong too because someo= ne could have done what they wanted but still needed the () around it. Say for an example debugging if :). >>From gcc-bugs-return-568436-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 22:39:52 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 41797 invoked by alias); 11 Jul 2017 22:39:52 -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 41749 invoked by uid 48); 11 Jul 2017 22:39:48 -0000 From: "babokin at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81403] New: wrong code at -O3 Date: Tue, 11 Jul 2017 22:39:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: babokin 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: 2017-07/txt/msg00987.txt.bz2 Content-length: 1282 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81403 Bug ID: 81403 Summary: wrong code at -O3 Product: gcc Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- gcc rev250140, x86_64. > cat f.cpp #include short var_9 =3D 19581; unsigned char var_33 =3D 21; long int var_55 =3D 286697804684061197L; long int var_59 =3D -1962393262513510540L; long int var_71 =3D 4731868609112929952L; long int var_773 =3D -4784633456247777769L; short var_776 =3D 5894; long int var_1321 =3D 7573221950916697355L; unsigned char uc =3D 217; void foo() { if (var_55) var_71 =3D 0; if (var_9 !=3D ~(0 < uc)) var_773 =3D 0; else var_776 =3D 1 / ~var_9 * -1; if (var_33) var_59 =3D ~var_9 & 10393; var_1321 =3D ~var_9; } int main() { foo(); std::cout << "var_59 =3D " << var_59 << " (8320 expected)\n"; return 0; } > g++ -w -O3 -o out f.cpp; ./out var_59 =3D -19582 (8320 expected) > g++ -w -O2 -o out f.cpp; ./out var_59 =3D 8320 (8320 expected) > g++ -w -O0 -o out f.cpp; ./out var_59 =3D 8320 (8320 expected) >>From gcc-bugs-return-568437-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 23:13:04 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 102772 invoked by alias); 11 Jul 2017 23:13: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 102688 invoked by uid 48); 11 Jul 2017 23:12:57 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/81395] [5/6/7/8 Regression] basic_filebuf::overflow recurses and overflows stack Date: Tue, 11 Jul 2017 23:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: redi at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.5 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: 2017-07/txt/msg00988.txt.bz2 Content-length: 1809 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81395 --- Comment #9 from Jonathan Wakely --- (In reply to Paolo Carlini from comment #4) > Seems weird: -1 means uncommitted (per the comment before _M_set_buffer) = and > we also set _M_reading? I don't think we do that anywhere else. But we also don't use _M_set_buffer(0) (write mode) and _M_reading=3Dtrue (= read mode) anywhere else, and doing that makes no sense to me. This comment says that _M_set_buffer(0) means write mode: /** * This function sets the pointers of the internal buffer, both get * and put areas. Typically: * * __off =3D=3D egptr() - eback() upon underflow/uflow (@b read mod= e); * __off =3D=3D 0 upon overflow (@b write mode); * __off =3D=3D -1 upon open, setbuf, seekoff/pos (@b uncommitted m= ode). * * NB: epptr() - pbase() =3D=3D _M_buf_size - 1, since _M_buf_size * reflects the actual allocated memory and the last cell is reserved * for the overflow char of a full put area. */ void _M_set_buffer(streamsize __off) But we call that from xsgetn which is obviously a read operation. And this comment says _M_reading =3D=3D true means read mode: /** * _M_reading =3D=3D false && _M_writing =3D=3D false for @b uncommi= tted mode; * _M_reading =3D=3D true for @b read mode; * _M_writing =3D=3D true for @b write mode; * * NB: _M_reading =3D=3D true && _M_writing =3D=3D true is unused. */ bool _M_reading; bool _M_writing; And it also says we don't use both true at once. So calling _M_set_buffer(0) and setting _M_reading =3D=3D true is a contradiction, or the comments are = wrong. >>From gcc-bugs-return-568438-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 11 23:25:46 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 120111 invoked by alias); 11 Jul 2017 23:25: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 119949 invoked by uid 48); 11 Jul 2017 23:25:42 -0000 From: "paolo.carlini at oracle dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/81395] [5/6/7/8 Regression] basic_filebuf::overflow recurses and overflows stack Date: Tue, 11 Jul 2017 23: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: 8.0 X-Bugzilla-Keywords: 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: redi at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.5 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: 2017-07/txt/msg00989.txt.bz2 Content-length: 449 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81395 --- Comment #10 from Paolo Carlini --- Yes, I agree with your analysis, something seems wrong. I suspsect going to= a normal uncommitted mode, thus not setting _M_reading would largely work, bu= t I fear performance implications, etc. I would strongly recommend analyzing ne= xt what can wrong if _M_reading remains false after that (a) reading operation= ... >>From gcc-bugs-return-568439-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 02:40:04 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 108697 invoked by alias); 12 Jul 2017 02:40: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 105975 invoked by uid 48); 12 Jul 2017 02:39:58 -0000 From: "msebor at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/81402] unhelpful -Wparentheses suggestion for assignment from non-zero constant Date: Wed, 12 Jul 2017 02:40:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: enhancement X-Bugzilla-Who: msebor at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: 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: 2017-07/txt/msg00990.txt.bz2 Content-length: 493 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81402 --- Comment #4 from Martin Sebor --- In my opinion (at least in the constant case) the warning would be more meaningful if it pointed out the likely mistake of using assignment as oppo= sed to equality instead of (only) recommending how to suppress it. In general, I think the text of a warning should focus on making the problem clear, and suggestions for fixes should be given in the form of fix-it hint= s. >>From gcc-bugs-return-568440-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 02:43:12 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 130550 invoked by alias); 12 Jul 2017 02:43: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 126045 invoked by uid 48); 12 Jul 2017 02:43:08 -0000 From: "msebor at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/81404] New: suggested hints for standard C macros should avoid GCC predefined macros Date: Wed, 12 Jul 2017 02:43: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: msebor at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-07/txt/msg00991.txt.bz2 Content-length: 946 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81404 Bug ID: 81404 Summary: suggested hints for standard C macros should avoid GCC predefined macros Product: gcc Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: msebor at gcc dot gnu.org Target Milestone: --- The fix-it hints printed along with errors for standard C library macros li= ke INT_MAX suggest GCC predefined symbols like __INT_MAX__ over the standard symbols. They should suggest the latter (along with the header the symbol = is defined in). $ cat a.c && gcc -S -Wall a.c int i =3D INT_MAX; a.c:1:9: error: =E2=80=98INT_MAX=E2=80=99 undeclared here (not in a functio= n); did you mean =E2=80=98__INT_MAX__=E2=80=99? int i =3D INT_MAX; ^~~~~~~ __INT_MAX__ >>From gcc-bugs-return-568441-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 06:50:35 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 69785 invoked by alias); 12 Jul 2017 06:50: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 69645 invoked by uid 48); 12 Jul 2017 06:50:27 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/81021] stack-use-after-scope false positive error with exceptions Date: Wed, 12 Jul 2017 06:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: marxin 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: 2017-07/txt/msg00992.txt.bz2 Content-length: 1214 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81021 --- Comment #25 from Martin Li=C5=A1ka --- (In reply to Martin Li=C5=A1ka from comment #24) > Just run with current trunk and it works (it fails after a minute in > =3D=3D13736=3D=3DERROR: AddressSanitizer: stack-overflow on address 0x2ad= b9b406e48 > (pc 0x0000067d8638 bp 0x2adb9b408020 sp 0x2adb9b406e30 T1) > So I'm going to test gcc-7-branch and I hope this patch is missing: >=20 > commit 5b64e274ea8c9aaedcebc1d6ad285a11e64ab086 > Author: marxin > Date: Fri Jun 30 08:51:00 2017 +0000 >=20 > Call BUILT_IN_ASAN_HANDLE_NO_RETURN before BUILT_IN_UNWIND_RESUME (PR > sanitizer/81021). >=20=20=20=20=20 > 2017-06-30 Martin Liska >=20=20=20=20=20 > PR sanitizer/81021 > * g++.dg/asan/pr81021.C: New test. > 2017-06-30 Martin Liska >=20=20=20=20=20 > PR sanitizer/81021 > * tree-eh.c (lower_resx): Call BUILT_IN_ASAN_HANDLE_NO_RETURN > before BUILT_IN_UNWIND_RESUME when ASAN is used. Confirmed, having GCC 7.x and the patch fixes the issue. Will appear soon in backport. >>From gcc-bugs-return-568443-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 06:59:47 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 10742 invoked by alias); 12 Jul 2017 06:59: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 3681 invoked by uid 48); 12 Jul 2017 06:59:33 -0000 From: "avi@cloudius-systems.com" To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/81021] stack-use-after-scope false positive error with exceptions Date: Wed, 12 Jul 2017 06:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: avi@cloudius-systems.com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: 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: 2017-07/txt/msg00994.txt.bz2 Content-length: 155 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81021 --- Comment #26 from Avi Kivity --- Thanks a lot for handling this issue. >>From gcc-bugs-return-568442-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 06:59:07 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 128617 invoked by alias); 12 Jul 2017 06:59:05 -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 128273 invoked by uid 48); 12 Jul 2017 06:58:56 -0000 From: "glisse at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81403] wrong code at -O3 Date: Wed, 12 Jul 2017 06:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: wrong-code 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: 2017-07/txt/msg00993.txt.bz2 Content-length: 798 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81403 --- Comment #1 from Marc Glisse --- PRE losing "& 10393" at -O3 but not -O2 (the previous dumps are identical) @@ -611,6 +639,7 @@ ;; 6 [100.0%] (FALLTHRU,EXECUTABLE) # .MEM_21 =3D PHI <.MEM_26(5), .MEM_25(6)> # prephitmp_34 =3D PHI <_30(5), _30(6)> + # prephitmp_35 =3D PHI <_30(5), _30(6)> # VUSE <.MEM_21> var_33.4_11 =3D var_33D.35372; if (var_33.4_11 !=3D 0) @@ -624,9 +653,7 @@ ;; prev block 7, next block 9, flags: (NEW, REACHABLE, VISITED) ;; pred: 7 [54.0%] (TRUE_VALUE,EXECUTABLE) # RANGE [0, 10393] NONZERO 10393 - _29 =3D prephitmp_34 & 10393; - # RANGE [0, 10393] NONZERO 10393 - _15 =3D (long intD.12) _29; + _15 =3D (long intD.12) prephitmp_35; >>From gcc-bugs-return-568445-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 07:16:12 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 58037 invoked by alias); 12 Jul 2017 07:14: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 105799 invoked by uid 48); 12 Jul 2017 07:10:07 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/81405] New: [8 Regression] Invalid write of size 2 in line_corrections::add_hint(fixit_hint const*) (diagnostic-show-locus.c:1514) Date: Wed, 12 Jul 2017 07:14:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 7.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-07/txt/msg00996.txt.bz2 Content-length: 4454 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81405 Bug ID: 81405 Summary: [8 Regression] Invalid write of size 2 in line_corrections::add_hint(fixit_hint const*) (diagnostic-show-locus.c:1514) Product: gcc Version: 7.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: marxin at gcc dot gnu.org CC: dmalcolm at gcc dot gnu.org Target Milestone: --- Starting from David's r247548 I see: $ valgrind --leak-check=3Dyes --trace-children=3Dyes gcc /home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/init-excess-1.c -Wmissing-braces ... /home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/init-excess-1.c:17:1: not= e: (near initialization for =E2=80=98a5[3]=E2=80=99) =3D=3D30671=3D=3D Invalid write of size 2 =3D=3D30671=3D=3D at 0x4C32D53: memmove (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) =3D=3D30671=3D=3D by 0x1414D2E: (anonymous namespace)::line_corrections::add_hint(fixit_hint const*) (diagnostic-show-locus.c:1514) =3D=3D30671=3D=3D by 0x14171E4: print_trailing_fixits (diagnostic-show-l= ocus.c:1558) =3D=3D30671=3D=3D by 0x14171E4: print_line (diagnostic-show-locus.c:1780) =3D=3D30671=3D=3D by 0x14171E4: diagnostic_show_locus(diagnostic_context= *, rich_location*, diagnostic_t) (diagnostic-show-locus.c:1827) =3D=3D30671=3D=3D by 0x6BA9D7: c_diagnostic_finalizer(diagnostic_context= *, diagnostic_info*) (c-opts.c:166) =3D=3D30671=3D=3D by 0x1411CF8: diagnostic_report_diagnostic(diagnostic_= context*, diagnostic_info*) (diagnostic.c:979) =3D=3D30671=3D=3D by 0x141209E: diagnostic_impl(rich_location*, int, cha= r const*, __va_list_tag (*) [1], diagnostic_t) (diagnostic.c:1099) =3D=3D30671=3D=3D by 0x1412597: warning_at_rich_loc(rich_location*, int,= char const*, ...) (diagnostic.c:1214) =3D=3D30671=3D=3D by 0x61C031: pop_init_level(unsigned int, int, obstack= *, unsigned int) (c-typeck.c:8069) =3D=3D30671=3D=3D by 0x6474B9: c_parser_braced_init(c_parser*, tree_node= *, bool, obstack*) (c-parser.c:4443) =3D=3D30671=3D=3D by 0x64846C: c_parser_initializer(c_parser*) (c-parser= .c:4365) =3D=3D30671=3D=3D by 0x65575D: c_parser_declaration_or_fndef(c_parser*, = bool, bool, bool, bool, bool, tree_node**, vec, oacc_routine_data*, bool*) (c-parser.c:1933) =3D=3D30671=3D=3D by 0x65E4C3: c_parser_external_declaration(c_parser*) (c-parser.c:1470) =3D=3D30671=3D=3D Address 0x644247c is 0 bytes after a block of size 12 al= loc'd =3D=3D30671=3D=3D at 0x4C2E2AF: realloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) =3D=3D30671=3D=3D by 0x147BB4C: xrealloc (xmalloc.c:179) =3D=3D30671=3D=3D by 0x1414D01: ensure_capacity (diagnostic-show-locus.c= :1432) =3D=3D30671=3D=3D by 0x1414D01: (anonymous namespace)::line_corrections::add_hint(fixit_hint const*) (diagnostic-show-locus.c:1513) =3D=3D30671=3D=3D by 0x14171E4: print_trailing_fixits (diagnostic-show-l= ocus.c:1558) =3D=3D30671=3D=3D by 0x14171E4: print_line (diagnostic-show-locus.c:1780) =3D=3D30671=3D=3D by 0x14171E4: diagnostic_show_locus(diagnostic_context= *, rich_location*, diagnostic_t) (diagnostic-show-locus.c:1827) =3D=3D30671=3D=3D by 0x6BA9D7: c_diagnostic_finalizer(diagnostic_context= *, diagnostic_info*) (c-opts.c:166) =3D=3D30671=3D=3D by 0x1411CF8: diagnostic_report_diagnostic(diagnostic_= context*, diagnostic_info*) (diagnostic.c:979) =3D=3D30671=3D=3D by 0x141209E: diagnostic_impl(rich_location*, int, cha= r const*, __va_list_tag (*) [1], diagnostic_t) (diagnostic.c:1099) =3D=3D30671=3D=3D by 0x1412597: warning_at_rich_loc(rich_location*, int,= char const*, ...) (diagnostic.c:1214) =3D=3D30671=3D=3D by 0x61C031: pop_init_level(unsigned int, int, obstack= *, unsigned int) (c-typeck.c:8069) =3D=3D30671=3D=3D by 0x6474B9: c_parser_braced_init(c_parser*, tree_node= *, bool, obstack*) (c-parser.c:4443) =3D=3D30671=3D=3D by 0x64846C: c_parser_initializer(c_parser*) (c-parser= .c:4365) =3D=3D30671=3D=3D by 0x65575D: c_parser_declaration_or_fndef(c_parser*, = bool, bool, bool, bool, bool, tree_node**, vec, oacc_routine_data*, bool*) (c-parser.c:1933) ... And similar errors that eventually lead to memory corruption. >>From gcc-bugs-return-568444-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 07:16:03 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 607 invoked by alias); 12 Jul 2017 07:14:01 -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 110502 invoked by uid 48); 12 Jul 2017 07:12:33 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81401] False positive sprintf warning at O2 (-Wformat-overflow) Date: Wed, 12 Jul 2017 07:14:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 7.1.1 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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: 2017-07/txt/msg00995.txt.bz2 Content-length: 481 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81401 Martin Li=C5=A1ka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-07-12 CC| |marxin at gcc dot gnu.org Ever confirmed|0 |1 >>From gcc-bugs-return-568446-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 07:17:15 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 77365 invoked by alias); 12 Jul 2017 07:15: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 106942 invoked by uid 48); 12 Jul 2017 07:11:02 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81403] [8 Regression] wrong code at -O3 Date: Wed, 12 Jul 2017 07:15:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc short_desc 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: 2017-07/txt/msg00997.txt.bz2 Content-length: 793 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81403 Martin Li=C5=A1ka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-07-12 CC| |marxin at gcc dot gnu.org, | |rguenth at gcc dot gnu.org Summary|wrong code at -O3 |[8 Regression] wrong code | |at -O3 Ever confirmed|0 |1 --- Comment #2 from Martin Li=C5=A1ka --- Confirmed, started with r247596. >>From gcc-bugs-return-568448-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 07:17:36 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 35157 invoked by alias); 12 Jul 2017 07:17:34 -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 16108 invoked by uid 48); 12 Jul 2017 07:16:23 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/81021] stack-use-after-scope false positive error with exceptions Date: Wed, 12 Jul 2017 07:17:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: marxin 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: 2017-07/txt/msg00999.txt.bz2 Content-length: 409 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81021 --- Comment #27 from Martin Li=C5=A1ka --- (In reply to Avi Kivity from comment #26) > Thanks a lot for handling this issue. You're welcome, I'm happy that it's a known issue and I don't have to dig in the source base. It's quite large. Anyhow, do you know why I see the stack overflow with sanitizer? It is a kn= own issue? >>From gcc-bugs-return-568447-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 07:17:35 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 35062 invoked by alias); 12 Jul 2017 07:17: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 76491 invoked by uid 48); 12 Jul 2017 07:14:57 -0000 From: "glisse at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81403] [8 Regression] wrong code at -O3 Date: Wed, 12 Jul 2017 07:17:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: glisse at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: 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: 2017-07/txt/msg00998.txt.bz2 Content-length: 324 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81403 --- Comment #3 from Marc Glisse --- /* x & C -> x if we know that x & ~C =3D=3D 0. */ Not clear where it is getting the bogus range/nonzero information from, I thought we had fixed all the places reusing SSA_NAMEs with stale informatio= n. >>From gcc-bugs-return-568449-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 07:28:18 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 62634 invoked by alias); 12 Jul 2017 07:28: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 55797 invoked by uid 48); 12 Jul 2017 07:28:10 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/81400] Stack smashing not caught by stack protector strong and allowing me to stack smash Date: Wed, 12 Jul 2017 07:28: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.1.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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: 2017-07/txt/msg01000.txt.bz2 Content-length: 694 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81400 Martin Li=C5=A1ka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2017-07-12 CC| |marxin at gcc dot gnu.org Assignee|unassigned at gcc dot gnu.org |marxin at gcc dot g= nu.org Ever confirmed|0 |1 --- Comment #1 from Martin Li=C5=A1ka --- Confirmed, thanks for the example, I'll take a look. >>From gcc-bugs-return-568450-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 07:32:08 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 71760 invoked by alias); 12 Jul 2017 07:32: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 71670 invoked by uid 48); 12 Jul 2017 07:32:03 -0000 From: "avi@cloudius-systems.com" To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/81021] stack-use-after-scope false positive error with exceptions Date: Wed, 12 Jul 2017 07:32:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: avi@cloudius-systems.com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: 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: 2017-07/txt/msg01001.txt.bz2 Content-length: 473 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81021 --- Comment #28 from Avi Kivity --- It's a combination of several things: 1. We use antlr to generate a parser. The generated code allocates many loc= al variables in the same function 2. use-after-scope disabled -fstack-reuse=3Dall 3. ASAN is quite liberal with stack padding 4. We also use user-level threads with just 128k of stack The combination of all four overflowed our poor stack. >>From gcc-bugs-return-568451-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 07:47:53 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 109015 invoked by alias); 12 Jul 2017 07:47:52 -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 108965 invoked by uid 48); 12 Jul 2017 07:47:48 -0000 From: "dcb314 at hotmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/81406] New: ice in check_die, at dwarf2out.c:6185 Date: Wed, 12 Jul 2017 07:47:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: lto X-Bugzilla-Version: 7.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dcb314 at hotmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc 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: 2017-07/txt/msg01002.txt.bz2 Content-length: 1616 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81406 Bug ID: 81406 Summary: ice in check_die, at dwarf2out.c:6185 Product: gcc Version: 7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: lto Assignee: unassigned at gcc dot gnu.org Reporter: dcb314 at hotmail dot com CC: marxin at gcc dot gnu.org Target Milestone: --- Created attachment 41725 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D41725&action=3Dedit x86_64 object module The attached object module, when compiled by recent gcc, does this: $ /home/dcb/gcc/results/bin/gcc -g -flto -shared dp.o=20 Duplicate attributes in DIE: DIE 0: DW_TAG_subprogram (0x7f03e39ffd20) abbrev id: 0 offset: 0 mark: 0 DW_AT_name: "efidp_node_size.part.0" DW_AT_prototyped: 1 DW_AT_type: die -> 0 (0x7f03e3d30190) DW_AT_artificial: 1 DW_AT_inline: 3 DW_AT_artificial: 1 DIE 0: DW_TAG_formal_parameter (0x7f03e39ffd70) abbrev id: 0 offset: 0 mark: 0 DW_AT_name: "dn" DW_AT_decl_file: "/home/dcb/rpmbuild/BUILD/efivar-31/src/include/efivar/ef ivar-dp.h" (0) DW_AT_decl_line: 821 DW_AT_type: die -> 0 (0x7f03e396c000) during IPA pass: inline In function =E2=80=98efidp_node_size.part.0=E2=80=99: lto1: internal compiler error: in check_die, at dwarf2out.c:6185 0x6e520e check_die ../../trunk/gcc/dwarf2out.c:6185 0x713d35 dwarf2out_abstract_function ../../trunk/gcc/dwarf2out.c:21672 0xbe0c42 expand_call_inline ../../trunk/gcc/tree-inline.c:4923 >>From gcc-bugs-return-568452-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 08:18:33 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 42074 invoked by alias); 12 Jul 2017 08:18: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 42050 invoked by uid 48); 12 Jul 2017 08:18:29 -0000 From: "gjl at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/81407] New: [avr] Diagnose if a variable in progmem needs constructing. Date: Wed, 12 Jul 2017 08:18:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gjl at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-07/txt/msg01003.txt.bz2 Content-length: 710 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81407 Bug ID: 81407 Summary: [avr] Diagnose if a variable in progmem needs constructing. Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: gjl at gcc dot gnu.org Target Milestone: --- avr-g++ might decide to pop up a constructor for a const variable in progme= m, shredding the assumption that the object is not written to at run-time. Diagnose such situations as the object will reside in .rodata then instead = of in .progmem.data. >>From gcc-bugs-return-568453-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 08:19:11 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 43222 invoked by alias); 12 Jul 2017 08:19:10 -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 43098 invoked by uid 48); 12 Jul 2017 08:19:05 -0000 From: "gjl at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/81407] [avr] Diagnose if a variable in progmem needs constructing. Date: Wed, 12 Jul 2017 08:19:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: unknown X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: enhancement X-Bugzilla-Who: gjl at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P5 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: keywords cf_gcctarget priority bug_severity 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: 2017-07/txt/msg01004.txt.bz2 Content-length: 464 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81407 Georg-Johann Lay changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |diagnostic Target| |avr Priority|P3 |P5 Severity|normal |enhancement >>From gcc-bugs-return-568454-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 08:26:36 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 80395 invoked by alias); 12 Jul 2017 08:26: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 80314 invoked by uid 48); 12 Jul 2017 08:26:31 -0000 From: "krister.walfridsson at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81388] Incorrect code generation with -O1 -fno-strict-overflow Date: Wed, 12 Jul 2017 08:26:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: krister.walfridsson at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: 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: 2017-07/txt/msg01005.txt.bz2 Content-length: 1192 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81388 krister.walfridsson at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |krister.walfridsson at gma= il dot c | |om --- Comment #5 from krister.walfridsson at gmail dot com --- Comment #1 says that "-fno-strict-overflow Does not effect Pointers", but t= he manual says for -fstrict-overflow: "This option also allows the compiler to assume strict pointer semantics: g= iven a pointer to an object, if adding an offset to that pointer does not produc= e a pointer to the same object, the addition is undefined. This permits the compiler to conclude that p + u > p is always true for a pointer p and unsi= gned integer u. This assumption is only valid because pointer wraparound is undefined, as the expression is false if p + u overflows using twos complem= ent arithmetic." At least I read this as -fno-strict-overflow permit pointer overflow too. Is that incorrect? If so, then I think the manual should be corrected/clarifie= d... >>From gcc-bugs-return-568455-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 08:28:05 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 83193 invoked by alias); 12 Jul 2017 08:28:05 -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 83052 invoked by uid 48); 12 Jul 2017 08:27:59 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/81400] Stack smashing not caught by stack protector strong and allowing me to stack smash Date: Wed, 12 Jul 2017 08:28: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.1.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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: 2017-07/txt/msg01006.txt.bz2 Content-length: 2501 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81400 Martin Li=C5=A1ka changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |uros at gcc dot gnu.org --- Comment #2 from Martin Li=C5=A1ka --- So there are 2 issue I can see: 1) Using -mstack-protector-guard=3Dtls (which is default for recent glibc) = causes usage of %fs:40 as a canary value. However as it does not cooperate with __guard_setup it has 0 as canary value. That's reason why your buffer overf= low is not caught (and one needs to assign a non-zero value: data[SMASH_ALIGN]= =3D'f'; I don't know how should be responsible for a set-up of the register as it's= a per thread value. Uros can you please help? 2) We have in gcc.c: #ifndef LINK_SSP_SPEC #ifdef TARGET_LIBC_PROVIDES_SSP #define LINK_SSP_SPEC "%{fstack-protector|fstack-protector-all" \ "|fstack-protector-strong|fstack-protector-explicit:= }" #else #define LINK_SSP_SPEC "%{fstack-protector|fstack-protector-all" \ "|fstack-protector-strong|fstack-protector-explicit"= \ ":-lssp_nonshared -lssp}" #endif #endif That is wrong when one uses: $ gcc smashme.c -fstack-protector-all -mstack-protector-guard=3Dglobal /tmp/ccq3aEcz.o: In function `smashme': smashme.c:(.text+0xb): undefined reference to `__stack_chk_guard' smashme.c:(.text+0x59): undefined reference to `__stack_chk_guard' /tmp/ccq3aEcz.o: In function `main': smashme.c:(.text+0x7b): undefined reference to `__stack_chk_guard' smashme.c:(.text+0x94): undefined reference to `__stack_chk_guard' collect2: error: ld returned 1 exit status which should be fixed by: diff --git a/gcc/gcc.c b/gcc/gcc.c index e8e3d6687c3..0043f86d8d2 100644 --- a/gcc/gcc.c +++ b/gcc/gcc.c @@ -869,7 +869,8 @@ proper position among the other output files. */ #ifndef LINK_SSP_SPEC #ifdef TARGET_LIBC_PROVIDES_SSP #define LINK_SSP_SPEC "%{fstack-protector|fstack-protector-all" \ - "|fstack-protector-strong|fstack-protector-explicit:= }" + "|fstack-protector-strong|fstack-protector-explicit:= " \ + "%{mstack-protector-guard=3Dglobal:-lssp}}" #else #define LINK_SSP_SPEC "%{fstack-protector|fstack-protector-all" \ "|fstack-protector-strong|fstack-protector-explicit"= \ >>From gcc-bugs-return-568456-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 08:46:03 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 84585 invoked by alias); 12 Jul 2017 08:46:01 -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 84310 invoked by uid 48); 12 Jul 2017 08:45:45 -0000 From: "jak@jak-linux.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/81408] New: Lots of new -Wunsafe-loop-optimizations warnings with 7 compared to 6 Date: Wed, 12 Jul 2017 08: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: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jak@jak-linux.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-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: 2017-07/txt/msg01007.txt.bz2 Content-length: 1088 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81408 Bug ID: 81408 Summary: Lots of new -Wunsafe-loop-optimizations warnings with 7 compared to 6 Product: gcc Version: 7.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: jak@jak-linux.org Target Milestone: --- Created attachment 41726 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D41726&action=3Dedit Minimized example Compiling a recent apt with g++-7 causes a lot more unsafe loop optimizatio= ns warnings than g++ 6 did (134 vs 8). That's a massive regression. 7.1.0 build log: https://launchpadlibrarian.net/327296659/buildlog_ubuntu-artful-i386.apt_1.= 5~beta1_BUILDING.txt.gz 6.3.0 build log: https://launchpadlibrarian.net/326714445/buildlog_ubuntu-artful-i386.apt_1.= 5~beta1_BUILDING.txt.gz It seems these are for-each kind of loops. I attached a simple minimized example from one of the cases mentioned in the log. >>From gcc-bugs-return-568457-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 08:46:53 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 89898 invoked by alias); 12 Jul 2017 08:46:53 -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 89746 invoked by uid 48); 12 Jul 2017 08:46:48 -0000 From: "jak@jak-linux.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/81408] Lots of new -Wunsafe-loop-optimizations warnings with 7 compared to 6 Date: Wed, 12 Jul 2017 08:46:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jak@jak-linux.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-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: 2017-07/txt/msg01008.txt.bz2 Content-length: 246 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81408 --- Comment #1 from Julian Andres Klode --- Created attachment 41727 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D41727&action=3Dedit preprocessed source of a.cc >>From gcc-bugs-return-568458-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 08:48:52 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 93785 invoked by alias); 12 Jul 2017 08:48:52 -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 93643 invoked by uid 48); 12 Jul 2017 08:48:47 -0000 From: "jak@jak-linux.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/81408] Lots of new -Wunsafe-loop-optimizations warnings with 7 compared to 6 Date: Wed, 12 Jul 2017 08:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jak@jak-linux.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: 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: 2017-07/txt/msg01009.txt.bz2 Content-length: 4371 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81408 --- Comment #2 from Julian Andres Klode --- Build log with -v: Using built-in specs. COLLECT_GCC=3D/usr/bin/g++-7 OFFLOAD_TARGET_NAMES=3Dnvptx-none OFFLOAD_TARGET_DEFAULT=3D1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion=3D'Debian 7.1.0-9' --with-bugurl=3Dfile:///usr/share/doc/gcc-7/README.Bugs --enable-languages=3Dc,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=3D/u= sr --with-gcc-major-version-only --program-suffix=3D-7 --program-prefix=3Dx86_64-linux-gnu- --enable-shared --enable-linker-build-= id --libexecdir=3D/usr/lib --without-included-gettext --enable-threads=3Dposix --libdir=3D/usr/lib --enable-nls --with-sysroot=3D/ --enable-clocale=3Dgnu --enable-libstdcxx-debug --enable-libstdcxx-time=3Dyes --with-default-libstdcxx-abi=3Dnew --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib --enable-objc-gc=3Dauto --enable-multiarch --disable-werror --with-arch-32=3Di686 --with-abi=3Dm64 --with-multilib-list=3Dm32,m64,mx32 --enable-multilib --with-tune=3Dgeneric --enable-offload-targets=3Dnvptx-none --without-cuda-driver --enable-checking=3Drelease --build=3Dx86_64-linux-gnu --host=3Dx86_64-linu= x-gnu --target=3Dx86_64-linux-gnu Thread model: posix gcc version 7.1.0 (Debian 7.1.0-9)=20 COLLECT_GCC_OPTIONS=3D'-v' '-save-temps' '-c' '-O2' '-Wunsafe-loop-optimiza= tions' '-shared-libgcc' '-mtune=3Dgeneric' '-march=3Dx86-64' /usr/lib/gcc/x86_64-linux-gnu/7/cc1plus -E -quiet -v -imultiarch x86_64-linux-gnu -D_GNU_SOURCE a.cc -mtune=3Dgeneric -march=3Dx86-64 -Wunsafe-loop-optimizations -O2 -fpch-preprocess -o a.ii ignoring duplicate directory "/usr/include/x86_64-linux-gnu/c++/7" ignoring nonexistent directory "/usr/local/include/x86_64-linux-gnu" ignoring nonexistent directory "/usr/lib/gcc/x86_64-linux-gnu/7/../../../../x86_64-linux-gnu/include" #include "..." search starts here: #include <...> search starts here: /usr/include/c++/7 /usr/include/x86_64-linux-gnu/c++/7 /usr/include/c++/7/backward /usr/lib/gcc/x86_64-linux-gnu/7/include /usr/local/include /usr/lib/gcc/x86_64-linux-gnu/7/include-fixed /usr/include/x86_64-linux-gnu /usr/include End of search list. COLLECT_GCC_OPTIONS=3D'-v' '-save-temps' '-c' '-O2' '-Wunsafe-loop-optimiza= tions' '-shared-libgcc' '-mtune=3Dgeneric' '-march=3Dx86-64' /usr/lib/gcc/x86_64-linux-gnu/7/cc1plus -fpreprocessed a.ii -quiet -dumpba= se a.cc -mtune=3Dgeneric -march=3Dx86-64 -auxbase a -O2 -Wunsafe-loop-optimiza= tions -version -o a.s GNU C++14 (Debian 7.1.0-9) version 7.1.0 (x86_64-linux-gnu) compiled by GNU C version 7.1.0, GMP version 6.1.2, MPFR version 3.= 1.5, MPC version 1.0.3, isl version isl-0.18-GMP GGC heuristics: --param ggc-min-expand=3D100 --param ggc-min-heapsize=3D131= 072 GNU C++14 (Debian 7.1.0-9) version 7.1.0 (x86_64-linux-gnu) compiled by GNU C version 7.1.0, GMP version 6.1.2, MPFR version 3.= 1.5, MPC version 1.0.3, isl version isl-0.18-GMP GGC heuristics: --param ggc-min-expand=3D100 --param ggc-min-heapsize=3D131= 072 Compiler executable checksum: 3681302eda59faba4e53a905eca4bf72 a.cc: In function =E2=80=98void ShowHelpListCommands(const std::vector&)=E2=80=99: a.cc:11:24: warning: missed loop optimization, the loop counter may overflow [-Wunsafe-loop-optimizations] for (auto const &c: Cmds) ^~~~ COLLECT_GCC_OPTIONS=3D'-v' '-save-temps' '-c' '-O2' '-Wunsafe-loop-optimiza= tions' '-shared-libgcc' '-mtune=3Dgeneric' '-march=3Dx86-64' as -v --64 -o a.o a.s GNU assembler version 2.28 (x86_64-linux-gnu) using BFD version (GNU Binuti= ls for Debian) 2.28 COMPILER_PATH=3D/usr/lib/gcc/x86_64-linux-gnu/7/:/usr/lib/gcc/x86_64-linux-= gnu/7/:/usr/lib/gcc/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/7/:/usr= /lib/gcc/x86_64-linux-gnu/ LIBRARY_PATH=3D/usr/lib/gcc/x86_64-linux-gnu/7/:/usr/lib/gcc/x86_64-linux-g= nu/7/../../../x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/7/../../../..= /lib/:/lib/x86_64-linux-gnu/:/lib/../lib/:/usr/lib/x86_64-linux-gnu/:/usr/l= ib/../lib/:/usr/lib/gcc/x86_64-linux-gnu/7/../../../:/lib/:/usr/lib/ COLLECT_GCC_OPTIONS=3D'-v' '-save-temps' '-c' '-O2' '-Wunsafe-loop-optimiza= tions' '-shared-libgcc' '-mtune=3Dgeneric' '-march=3Dx86-64' >>From gcc-bugs-return-568459-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 08:50:55 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 101543 invoked by alias); 12 Jul 2017 08:50: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 101029 invoked by uid 48); 12 Jul 2017 08:50:50 -0000 From: "jak@jak-linux.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/81408] Lots of new -Wunsafe-loop-optimizations warnings with 7 compared to 6 Date: Wed, 12 Jul 2017 08:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jak@jak-linux.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: 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: 2017-07/txt/msg01010.txt.bz2 Content-length: 189 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81408 --- Comment #3 from Julian Andres Klode --- 7.1.0-9 corresponds to "SVN 20170705 (r250006) from the gcc-7-branch." >>From gcc-bugs-return-568460-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 08:56:00 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 7796 invoked by alias); 12 Jul 2017 08:56: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 7739 invoked by uid 48); 12 Jul 2017 08:55:54 -0000 From: "jak@jak-linux.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/81408] Lots of new -Wunsafe-loop-optimizations warnings with 7 compared to 6 Date: Wed, 12 Jul 2017 08:56:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jak@jak-linux.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: 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: 2017-07/txt/msg01011.txt.bz2 Content-length: 238 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81408 --- Comment #4 from Julian Andres Klode --- Note that apt has 1219 loops, so 134 is almost 11% of the loops causing the warning, compared to about 0.7% (8) before. >>From gcc-bugs-return-568461-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 09:05:57 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 79441 invoked by alias); 12 Jul 2017 09:05: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 79390 invoked by uid 48); 12 Jul 2017 09:05:52 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/81406] ice in check_die, at dwarf2out.c:6185 Date: Wed, 12 Jul 2017 09:05:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: lto X-Bugzilla-Version: 7.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed Message-ID: 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: 2017-07/txt/msg01012.txt.bz2 Content-length: 627 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81406 Martin Li=C5=A1ka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Last reconfirmed| |2017-07-12 Ever confirmed|0 |1 --- Comment #1 from Martin Li=C5=A1ka --- Can you please provide a pre-processed source file that was used to generate the module. As LTO ABI is not stabilized, it's impossible to bisect. >>From gcc-bugs-return-568462-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 09:20:55 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 39297 invoked by alias); 12 Jul 2017 09:20: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 39227 invoked by uid 48); 12 Jul 2017 09:20:49 -0000 From: "gjl at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/81073] [5/6/7/8 Regression] link failure as C++ misses to instanciate some objects Date: Wed, 12 Jul 2017 09:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.1.1 X-Bugzilla-Keywords: link-failure X-Bugzilla-Severity: normal X-Bugzilla-Who: gjl at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jason at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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: 2017-07/txt/msg01013.txt.bz2 Content-length: 1057 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81073 --- Comment #10 from Georg-Johann Lay --- (In reply to Jason Merrill from comment #9) > Created attachment 41711 [details] > patch to error on progmem with dynamic init >=20 > Does this do what you had in mind? Some situations are diagnosed, but already something like in this PR passes your test und dynamically initializes __c in .rodata: #define PROGMEM __attribute__((__progmem__)) // A string in flash #define PSTR(str) \ (__extension__({ \ static const char __c[] =3D (str); \ &__c[0]; \ })) typedef struct { char id; const char *labl; } menu_t; const menu_t* setup_Flash (void) { static const menu_t menu PROGMEM =3D { 123, PSTR ("in Flash") }; return &menu; } int main(){} So either this should be diagnosed or deflate similar to const menu_t* setup_RAM (void) { static const menu_t menu PROGMEM =3D { 123, "in RAM" }; return &menu; } >>From gcc-bugs-return-568463-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 09:22:00 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 40556 invoked by alias); 12 Jul 2017 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 40508 invoked by uid 48); 12 Jul 2017 09:21:56 -0000 From: "kristerw at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81409] New: Inefficient loops generated from range-v3 code Date: Wed, 12 Jul 2017 09:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kristerw at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-07/txt/msg01014.txt.bz2 Content-length: 1699 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81409 Bug ID: 81409 Summary: Inefficient loops generated from range-v3 code Product: gcc Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: kristerw at gcc dot gnu.org Target Milestone: --- Created attachment 41728 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D41728&action=3Dedit Preprocessed file for run_range() The range-v3 (https://github.com/ericniebler/range-v3) function long run_range(std::vector const &lengths, long to_find) { auto const found_index =3D ranges::distance(lengths | ranges::view::transform(ranges::convert_to{}) | ranges::view::partial_sum() | ranges::view::take_while([=3D](auto const i) { return !(to_find < i); })); return found_index; } is generated as slow code with GCC, needing 3x the time to run compared to = the code generated by LLVM (when compiled with "-O3 -std=3Dc++14 -DNDEBUG"). The calculation done in run_range() is the equivalent of long run_forloop(std::vector const &vec, long to_find) { long len =3D vec.end() - vec.begin(); const int *p =3D &vec[0]; long i, acc =3D 0; for (i =3D 0; i < len; i++) { acc +=3D p[i]; if (to_find < acc) break; } return i; } and LLVM manages to generate similar code for both functions, while GCC see= ms to be confused by the run_range() loop and generates extra comparisions and= a somewhat messy code flow... >>From gcc-bugs-return-568464-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 09:24:57 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 47964 invoked by alias); 12 Jul 2017 09:24: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 47732 invoked by uid 48); 12 Jul 2017 09:24:21 -0000 From: "gjl at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/81073] [5/6/7/8 Regression] link failure as C++ misses to instanciate some objects Date: Wed, 12 Jul 2017 09:24:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.1.1 X-Bugzilla-Keywords: link-failure X-Bugzilla-Severity: normal X-Bugzilla-Who: gjl at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jason at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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: 2017-07/txt/msg01015.txt.bz2 Content-length: 471 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81073 --- Comment #11 from Georg-Johann Lay --- ...oops, I missed the PROGMEM in PSTR definition. Should read: // A string in flash #define PSTR(str) \ (__extension__({ \ static const char __c[] PROGMEM =3D (str); \ &__c[0]; \ })) but still no error. >>From gcc-bugs-return-568465-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 09:38:56 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 20356 invoked by alias); 12 Jul 2017 09:38: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 20263 invoked by uid 48); 12 Jul 2017 09:38:50 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/81408] Lots of new -Wunsafe-loop-optimizations warnings with 7 compared to 6 Date: Wed, 12 Jul 2017 09:38:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc 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: 2017-07/txt/msg01016.txt.bz2 Content-length: 1478 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81408 Martin Li=C5=A1ka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-07-12 CC| |amker at gcc dot gnu.org, | |glisse at gcc dot gnu.org, | |marxin at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #5 from Martin Li=C5=A1ka --- Confirmed, I reduced one test-case: $ cat pr81408.ii template class d { b e; public: int operator* () {} void operator++ () { ++e; } b base () { return e; } }; template bool operator!=3D (d i, d j) { return i.base () - j.base (); } template class k; template struct m; template struct m> { using l =3D a *; }; struct p : m> { d begin (); d end (); } n; void o () { for (auto c : n) ; } Which started to be recognized with r242638. And I also noticed the original unreduced test-case started to be diagnosed with r238641. That said it's probably better optimizer work that shows more warnings, am I right? >>From gcc-bugs-return-568466-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 10:16:51 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 93027 invoked by alias); 12 Jul 2017 10:16: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 92754 invoked by uid 48); 12 Jul 2017 10:16:40 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/81408] Lots of new -Wunsafe-loop-optimizations warnings with 7 compared to 6 Date: Wed, 12 Jul 2017 10:16:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: 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: 2017-07/txt/msg01017.txt.bz2 Content-length: 1252 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81408 --- Comment #6 from Martin Li=C5=A1ka --- And there's sample which started to be reported with Bin's revision r238641: namespace a { void b () __attribute__ ((__noreturn__)); template struct d; template struct d { typedef e f; }; struct g { template using i =3D h *; }; } using a::d; template class k { j l; public: typename d::f operator* () {} void operator++ () { ++l; } j aa () { return l; } }; template bool operator!=3D (k o, k p2) { return o.aa () !=3D p2.aa (); } struct p; namespace a { struct F { struct q { using ai =3D g::i

; }; using r =3D q::ai; }; class H { public: k begin (); k end (); }; int s; class I { public: void aq (char) { if (s) b (); } }; class u : public I { public: void operator<< (u o (u)) { o (*this); } u operator<< (void *); }; template at av (au o) { o.aq ('\n'); } u ax; } struct p { char *ay; }; a::H t; void ShowHelpListCommands () { for (auto c : t) a::ax << c.ay << a::av; } >>From gcc-bugs-return-568467-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 10:46:07 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 58505 invoked by alias); 12 Jul 2017 10:46:06 -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 49633 invoked by uid 48); 12 Jul 2017 10:45:56 -0000 From: "amker at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/81408] Lots of new -Wunsafe-loop-optimizations warnings with 7 compared to 6 Date: Wed, 12 Jul 2017 10:46:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: amker at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: amker at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: 2017-07/txt/msg01018.txt.bz2 Content-length: 1809 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81408 amker at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |amker at gcc dot gn= u.org --- Comment #7 from amker at gcc dot gnu.org --- (In reply to Martin Li=C5=A1ka from comment #6) > And there's sample which started to be reported with Bin's revision r2386= 41: >=20 > namespace a { > void b () __attribute__ ((__noreturn__)); > template struct d; > template struct d > { > typedef e f; > }; > struct g > { > template using i =3D h *; > }; > } > using a::d; > template class k > { > j l; >=20 > public: > typename d::f operator* () {} > void operator++ () { ++l; } > j > aa () > { > return l; > } > }; > template > bool > operator!=3D (k o, k p2) > { > return o.aa () !=3D p2.aa (); > } > struct p; > namespace a { > struct F > { > struct q > { > using ai =3D g::i

; > }; > using r =3D q::ai; > }; > class H > { > public: > k begin (); > k end (); > }; > int s; > class I > { > public: > void > aq (char) > { > if (s) > b (); > } > }; > class u : public I > { > public: > void > operator<< (u o (u)) > { > o (*this); > } > u operator<< (void *); > }; > template > at > av (au o) > { > o.aq ('\n'); > } > u ax; > } > struct p > { > char *ay; > }; > a::H t; > void > ShowHelpListCommands () > { > for (auto c : t) > a::ax << c.ay << a::av; > } Yes, it's very likely my fault. Thanks for reducing the test case. I will investigate it. >>From gcc-bugs-return-568468-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 11:26:03 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 110219 invoked by alias); 12 Jul 2017 11:26: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 110171 invoked by uid 48); 12 Jul 2017 11:25:58 -0000 From: "gcc at sjor dot sg" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/81410] New: O3 breaks code Date: Wed, 12 Jul 2017 11:26:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.1.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gcc at sjor dot sg X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone 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: 2017-07/txt/msg01019.txt.bz2 Content-length: 878 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81410 Bug ID: 81410 Summary: O3 breaks code Product: gcc Version: 7.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: gcc at sjor dot sg Target Milestone: --- Created attachment 41729 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D41729&action=3Dedit Minimal test case See attached code. Tested on Ubuntu's gcc 6.2.0, Debian's 6.3.0, Arch's 7.1= .1. Testcase is about as minimal as I could get it. Compile with -O3 -std=3Dc++11. As you see, it extracts data from a vector to two vectors. Then, it checks whether the vector.first and vector have the same values. If so, it exit(1)'s which confirms the bug is present. >>From gcc-bugs-return-568469-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 11:30:54 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 114320 invoked by alias); 12 Jul 2017 11:30: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 114215 invoked by uid 48); 12 Jul 2017 11:30:45 -0000 From: "gcc at sjor dot sg" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/81410] O3 breaks code Date: Wed, 12 Jul 2017 11:30:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.1.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gcc at sjor dot sg X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: 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: 2017-07/txt/msg01020.txt.bz2 Content-length: 168 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81410 --- Comment #1 from Sjors Gielen --- This is on x86_64 by the way. Doesn't happen with -m32. >>From gcc-bugs-return-568470-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 11:38:04 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 130592 invoked by alias); 12 Jul 2017 11:38:04 -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 130496 invoked by uid 48); 12 Jul 2017 11:38:00 -0000 From: "m-ou.se@m-ou.se" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/81410] O3 breaks code Date: Wed, 12 Jul 2017 11:38:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.1.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: m-ou.se@m-ou.se X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-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: 2017-07/txt/msg01021.txt.bz2 Content-length: 675 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81410 Maurice Bos changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |m-ou.se@m-ou.se --- Comment #2 from Maurice Bos --- Created attachment 41730 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D41730&action=3Dedit Test case without using any standard headers Here's a test case which fails in the same way (on x86_64, Gcc 7.1.1), but without using any standard headers. (No std::pair or std::vector.) Only fai= ls with -O3, with any -std=3D. >>From gcc-bugs-return-568472-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 11:41:14 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 23720 invoked by alias); 12 Jul 2017 11:41: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 23444 invoked by uid 48); 12 Jul 2017 11:41:09 -0000 From: "gcc at sjor dot sg" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/81410] O3 breaks code Date: Wed, 12 Jul 2017 11:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.1.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gcc at sjor dot sg X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: 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: 2017-07/txt/msg01023.txt.bz2 Content-length: 265 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81410 --- Comment #3 from Sjors Gielen --- A trivial workaround is put inside the first loop: std::cout << ""; I suppose this prevents loop optimization by introducing potential side effects. >>From gcc-bugs-return-568471-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 11:41:05 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 22921 invoked by alias); 12 Jul 2017 11:41:05 -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 22871 invoked by uid 48); 12 Jul 2017 11:41:01 -0000 From: "ian at rhymneyconsulting dot co.uk" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/81411] New: intrinsic polymorphic assignment run time error Date: Wed, 12 Jul 2017 11: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.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ian at rhymneyconsulting dot co.uk X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: 2017-07/txt/msg01022.txt.bz2 Content-length: 1043 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81411 Bug ID: 81411 Summary: intrinsic polymorphic assignment run time error Product: gcc Version: 7.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: ian at rhymneyconsulting dot co.uk Target Milestone: --- Created attachment 41731 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D41731&action=3Dedit This is the total set of files. I get the following error at run time c:\document\fortran\fourth_edition\examples>ch2806_gfortran.exe calling display subroutine Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: #0 0xffffffff #1 0xffffffff #2 0xffffffff #3 0xffffffff #4 0xffffffff #5 0xffffffff #6 0xffffffff #7 0xffffffff #8 0xffffffff #9 0xffffffff #10 0xffffffff #11 0xffffffff #12 0xffffffff #13 0xffffffff #14 0xffffffff >>From gcc-bugs-return-568473-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 11:44:47 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 34258 invoked by alias); 12 Jul 2017 11:44: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 34135 invoked by uid 48); 12 Jul 2017 11:44:41 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/81410] [5/6/7/8 Regression] -O3 breaks code Date: Wed, 12 Jul 2017 11:44:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.1.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc short_desc 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: 2017-07/txt/msg01024.txt.bz2 Content-length: 795 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81410 Martin Li=C5=A1ka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2017-07-12 CC| |jason at gcc dot gnu.org, | |marxin at gcc dot gnu.org Summary|O3 breaks code |[5/6/7/8 Regression] -O3 | |breaks code Ever confirmed|0 |1 --- Comment #4 from Martin Li=C5=A1ka --- Confirmed, started with r209313. >>From gcc-bugs-return-568474-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 12:19:18 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 78914 invoked by alias); 12 Jul 2017 12:19: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 78848 invoked by uid 48); 12 Jul 2017 12:19:13 -0000 From: "glisse at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/81409] Inefficient loops generated from range-v3 code Date: Wed, 12 Jul 2017 12:19:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: 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: 2017-07/txt/msg01025.txt.bz2 Content-length: 781 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81409 --- Comment #1 from Marc Glisse --- The most obvious thing I notice is [100.00%] [count: INV]: # it$_M_current_23 =3D PHI _20 =3D _7 =3D=3D it$_M_current_23; _5 =3D _20 | _53; if (_5 !=3D 0) goto ; [7.36%] [count: INV] else goto ; [92.64%] [count: INV] [92.60%] [count: INV]: _27 =3D it$_M_current_23 + 4; if (_7 !=3D _27) goto ; [3.75%] [count: INV] else goto ; [96.25%] [count: INV] where 7 -> 6 means that _7 =3D=3D _27 =3D=3D it$_M_current_23 so _5 !=3D 0 = has to be true. However, we do not thread that (at thread4 time, we go from 7 to 12 (empty latch) to 6 instead of directly to 6). >>From gcc-bugs-return-568475-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 12:36:51 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 52666 invoked by alias); 12 Jul 2017 12:36: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 49358 invoked by uid 48); 12 Jul 2017 12:36:46 -0000 From: "glisse at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/81410] [5/6/7/8 Regression] -O3 breaks code Date: Wed, 12 Jul 2017 12:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.1.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: glisse at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: 2017-07/txt/msg01026.txt.bz2 Content-length: 746 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81410 --- Comment #5 from Marc Glisse --- Seems related to vectorization. These lines look suspicious: vect__37.14_78 =3D MEM[(long int *)_30]; vect__37.15_72 =3D MEM[(long int *)_30 + 16B]; vect__37.16_70 =3D MEM[(long int *)_30 + 32B]; vect__37.17_68 =3D MEM[(long int *)_30 + 48B]; MEM[(long int *)_28] =3D vect__37.14_78; MEM[(long int *)_28 + 16B] =3D vect__37.15_72; MEM[(long int *)_28 + 32B] =3D vect__37.16_70; MEM[(long int *)_28 + 48B] =3D vect__37.17_68; where _30 is for b, _28 is for a, and I would expect to see gaps in the rea= ds from b (+24, +48, +72 instead of +16, +32 and +48). But I haven't checked, = this is only a first guess. >>From gcc-bugs-return-568476-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 12:37:34 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 78176 invoked by alias); 12 Jul 2017 12:37: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 76127 invoked by uid 48); 12 Jul 2017 12:37:29 -0000 From: "fjwyhzb at hotmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug libquadmath/81412] New: roundq Date: Wed, 12 Jul 2017 12:37:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libquadmath X-Bugzilla-Version: 7.1.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: fjwyhzb at hotmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-07/txt/msg01027.txt.bz2 Content-length: 1687 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81412 Bug ID: 81412 Summary: roundq Product: gcc Version: 7.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libquadmath Assignee: unassigned at gcc dot gnu.org Reporter: fjwyhzb at hotmail dot com Target Milestone: --- Created attachment 41732 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D41732&action=3Dedit roundq-bug.i $ cat roundq-bug.c #include #include int main(void) { double x =3D 2147483648.7; printf("roundq(%.1f) =3D %.1f\n", x, (double)roundq(x)); } $ gcc -save-temps -Wall -Wextra roundq-bug.c -lquadmath $ ./a.out roundq(2147483648.7) =3D 2147483648.7 $ gcc -v Using built-in specs. COLLECT_GCC=3Dgcc COLLECT_LTO_WRAPPER=3D/usr/lib/gcc/x86_64-pc-linux-gnu/7.1.1/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /build/gcc/src/gcc/configure --prefix=3D/usr --libdir=3D/u= sr/lib --libexecdir=3D/usr/lib --mandir=3D/usr/share/man --infodir=3D/usr/share/in= fo --with-bugurl=3Dhttps://bugs.archlinux.org/ --enable-languages=3Dc,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=3Dposix --enable-libmpx --with-system-zlib --with-isl --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=3Dgnu --disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object --enable-linker-build-id --enable-lto --enable-plugin --enable-install-libiberty --with-linker-hash-style=3Dgnu --enable-gnu-indirect-function --disable-multilib --disable-werror --enable-checking=3Drelease Thread model: posix gcc version 7.1.1 20170621 (GCC) >>From gcc-bugs-return-568478-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 13:01:29 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 22636 invoked by alias); 12 Jul 2017 13:01:28 -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 22230 invoked by uid 48); 12 Jul 2017 13:01:22 -0000 From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libquadmath/65757] gfortran gives incorrect result for anint with real*16 argument Date: Wed, 12 Jul 2017 13:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libquadmath X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: 2017-07/txt/msg01029.txt.bz2 Content-length: 442 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D65757 Jakub Jelinek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fjwyhzb at hotmail dot com --- Comment #14 from Jakub Jelinek --- *** Bug 81412 has been marked as a duplicate of this bug. *** >>From gcc-bugs-return-568477-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 13:01:19 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 21934 invoked by alias); 12 Jul 2017 13:01: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 21484 invoked by uid 48); 12 Jul 2017 13:00:53 -0000 From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libquadmath/81412] roundq Date: Wed, 12 Jul 2017 13:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libquadmath X-Bugzilla-Version: 7.1.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc resolution Message-ID: 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: 2017-07/txt/msg01028.txt.bz2 Content-length: 561 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81412 Jakub Jelinek changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |jakub at gcc dot gnu.org Resolution|--- |DUPLICATE --- Comment #1 from Jakub Jelinek --- Dup. *** This bug has been marked as a duplicate of bug 65757 *** >>From gcc-bugs-return-568479-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 13:02:06 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 24705 invoked by alias); 12 Jul 2017 13:02:06 -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 24236 invoked by uid 48); 12 Jul 2017 13:02:01 -0000 From: "space_sk8er8 at hotmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/81413] New: overloaded new and delete might not be called when dynamically linked with libstdc++ Date: Wed, 12 Jul 2017 13:02:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: space_sk8er8 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: 2017-07/txt/msg01030.txt.bz2 Content-length: 1707 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81413 Bug ID: 81413 Summary: overloaded new and delete might not be called when dynamically linked with libstdc++ Product: gcc Version: 7.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: space_sk8er8 at hotmail dot com Target Milestone: --- new and delete operator overloading might or might not work when compiled u= sing different compilers and different c++ standards. I used the following code to test the compilers. #include void * operator new(size_t size) { std::cout << "1\n"; return malloc(size); } void operator delete(void * ptr) noexcept { std::cout << "2\n"; free(ptr); } int main(void) { int *n1 =3D new int; delete n1; int *n2 =3D new int[10]; delete[] n2; } Here are the results I got from several compilers I have tested the code on. mingw-w64 official build - x86_64-7.1.0-release-posix-seh-rt_v5-rev0.7z c++11 1 2 c++14 1 clang x86_64 - v4.0.0 manually built without patches using the compiler abo= ve c++11 and c++14 1 2 msvc - platform toolset v141 & sdk v10.0.15063.0 /std:c++14 & /std:c++latest 1 2 1 2 All tests are performed on Windows 7. I can't test compilers on GNU/Linux OS because I don't have any VMs set up. Apparently, if -static or -static-libstdc++ is specified, it outputs the intended result. c++11 and c++14 1 2 1 2 More discussions at https://sourceforge.net/p/mingw-w64/bugs/634/ and https://stackoverflow.com/questions/44907098/c-new-and-delete-overloading >>From gcc-bugs-return-568480-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 13:07:35 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 48021 invoked by alias); 12 Jul 2017 13:07:34 -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 47984 invoked by uid 48); 12 Jul 2017 13:07:31 -0000 From: "yroux at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/80287] C++ crash with __attribute((may_alias)) Date: Wed, 12 Jul 2017 13:07:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: yroux at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: 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: 2017-07/txt/msg01031.txt.bz2 Content-length: 543 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D80287 Yvan Roux changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yroux at gcc dot gnu.org --- Comment #4 from Yvan Roux --- Hi Bernd, gcc-6-branch is impacted by this issue (observed on AArch64 target at r2501= 09, with regression introduced at r234768). I can prepare the backport if you whish. >>From gcc-bugs-return-568481-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 13:10:52 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 87291 invoked by alias); 12 Jul 2017 13:10:52 -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 69369 invoked by uid 48); 12 Jul 2017 13:10:48 -0000 From: "bernd.edlinger at hotmail dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/80287] C++ crash with __attribute((may_alias)) Date: Wed, 12 Jul 2017 13: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.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: bernd.edlinger at hotmail dot de X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: 2017-07/txt/msg01032.txt.bz2 Content-length: 378 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D80287 --- Comment #5 from Bernd Edlinger --- (In reply to Yvan Roux from comment #4) > Hi Bernd, >=20 > gcc-6-branch is impacted by this issue (observed on AArch64 target at > r250109, with regression introduced at r234768). I can prepare the backp= ort > if you whish. Yes, thanks, go ahead. >>From gcc-bugs-return-568482-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 13:54:11 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 15744 invoked by alias); 12 Jul 2017 13:54:10 -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 10885 invoked by uid 48); 12 Jul 2017 13:54:06 -0000 From: "fjwyhzb at hotmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug libquadmath/81412] roundq Date: Wed, 12 Jul 2017 13:54:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libquadmath X-Bugzilla-Version: 7.1.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: fjwyhzb at hotmail dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: 2017-07/txt/msg01033.txt.bz2 Content-length: 172 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81412 --- Comment #2 from Huang Zhibin --- Bug 65757 Status: UNCONFIRMED. How to fix this Bug? >>From gcc-bugs-return-568483-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 13:59:05 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 76576 invoked by alias); 12 Jul 2017 13:59:05 -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 76424 invoked by uid 48); 12 Jul 2017 13:59:01 -0000 From: "gjl at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/81407] [avr] Diagnose if a variable in progmem needs constructing. Date: Wed, 12 Jul 2017 13:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: unknown X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: enhancement X-Bugzilla-Who: gjl at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P5 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: 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: 2017-07/txt/msg01034.txt.bz2 Content-length: 431 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81407 Georg-Johann Lay changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Georg-Johann Lay --- Fixed in v8. >>From gcc-bugs-return-568484-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 13:59:11 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 77321 invoked by alias); 12 Jul 2017 13:59:10 -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 76727 invoked by uid 55); 12 Jul 2017 13:59:06 -0000 From: "gjl at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/81407] [avr] Diagnose if a variable in progmem needs constructing. Date: Wed, 12 Jul 2017 13:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: unknown X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: enhancement X-Bugzilla-Who: gjl at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P5 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: 2017-07/txt/msg01035.txt.bz2 Content-length: 491 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81407 --- Comment #2 from Georg-Johann Lay --- Author: gjl Date: Wed Jul 12 13:58:34 2017 New Revision: 250151 URL: https://gcc.gnu.org/viewcvs?rev=3D250151&root=3Dgcc&view=3Drev Log: PR target/81407 * config/avr/avr.c (avr_encode_section_info) [progmem && !TREE_READONLY]: Error if progmem object needs constructing. Modified: trunk/gcc/ChangeLog trunk/gcc/config/avr/avr.c >>From gcc-bugs-return-568485-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 14:01:55 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 85319 invoked by alias); 12 Jul 2017 14:01: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 85198 invoked by uid 48); 12 Jul 2017 14:01:51 -0000 From: "gjl at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/81073] [5/6/7/8 Regression] link failure as C++ misses to instantiate some objects Date: Wed, 12 Jul 2017 14:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.1.1 X-Bugzilla-Keywords: link-failure X-Bugzilla-Severity: normal X-Bugzilla-Who: gjl at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jason at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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: 2017-07/txt/msg01036.txt.bz2 Content-length: 480 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81073 --- Comment #12 from Georg-Johann Lay --- Thanks, (In reply to Jason Merrill from comment #9) > Created attachment 41711 [details] > patch to error on progmem with dynamic init >=20 > Does this do what you had in mind? Hi, thanks. Used to implement PR81407. FYI, problem above was that the test was inside "if DECL_INITIAL =3D=3D NUL= L".=20 When moved out of that condition, it works as expected. >>From gcc-bugs-return-568486-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 12 14:02:33 2017 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 90694 invoked by alias); 12 Jul 2017 14:02: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 90220 invoked by uid 48); 12 Jul 2017 14:02:29 -0000 From: "gjl at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/81407] [avr] Diagnose if a variable in progmem needs constructing. Date: Wed, 12 Jul 2017 14:02:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: unknown X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: enhancement X-Bugzilla-Who: gjl at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P5 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.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: 2017-07/txt/msg01037.txt.bz2 Content-length: 291 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81407 Georg-Johann Lay changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |8.0 >>From giada@giadaturri.it Wed Jul 12 14:03:00 2017 From: "Ester Hileman" To: gcc-bugs@gcc.gnu.org Subject: The Funds from Ester Hileman Date: Wed, 12 Jul 2017 14:03:00 -0000 Message-id: <4bf6bfb22a9698778ca8f406739f2f8d@NO-ID-FOUND.mhonarc.org> X-SW-Source: 2017-07/msg01038.html Content-length: 311 Hi Your email (gcc-bugs@gcc.gnu.org) was used as the destination of the transfer. The Transfer should appear in 3 days. Access key is DfgpU7FRo. You need to enter it to be able to view the attached file. Ester Hileman Attachment: e55b_Ester Hileman.docx Description: Attached file: e55b_Ester Hileman.docx