From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 106559 invoked by alias); 12 Nov 2018 12:04: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 Received: (qmail 106482 invoked by uid 48); 12 Nov 2018 12:04:36 -0000 From: "aoliva at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/81878] --disable-bootstrap --enable-languages=ada fails Date: Mon, 12 Nov 2018 12:04:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: ada X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: normal X-Bugzilla-Who: aoliva at gcc dot gnu.org X-Bugzilla-Status: REOPENED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01014.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81878 --- Comment #53 from Alexandre Oliva --- https://gcc.gnu.org/ml/gcc-patches/2018-11/msg00930.html >>From gcc-bugs-return-620858-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 12:20:47 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 107913 invoked by alias); 12 Nov 2018 12:20: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 107830 invoked by uid 48); 12 Nov 2018 12:20:39 -0000 From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/87985] Compile-time and memory hog w/ -O1 -ftree-slp-vectorize Date: Mon, 12 Nov 2018 12:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 8.2.1 X-Bugzilla-Keywords: compile-time-hog, memory-hog X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on component version assigned_to everconfirmed Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01015.txt.bz2 Content-length: 705 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87985 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2018-11-12 Component|rtl-optimization |tree-optimization Version|unknown |8.2.1 Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot = gnu.org Ever confirmed|0 |1 --- Comment #1 from Richard Biener --- I will take a look. >>From gcc-bugs-return-620859-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 12:27:40 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 20102 invoked by alias); 12 Nov 2018 12:27: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 20037 invoked by uid 48); 12 Nov 2018 12:27:36 -0000 From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/87985] Compile-time and memory hog w/ -O1 -ftree-slp-vectorize Date: Mon, 12 Nov 2018 12:27:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 8.2.1 X-Bugzilla-Keywords: compile-time-hog, memory-hog X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01016.txt.bz2 Content-length: 176 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87985 --- Comment #2 from Richard Biener --- It's split_constant_offset creating the large tree... >>From gcc-bugs-return-620860-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 12:32:10 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 30789 invoked by alias); 12 Nov 2018 12:32: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 30744 invoked by uid 48); 12 Nov 2018 12:32:05 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/52869] [DR 1207] "this" not being allowed in noexcept clauses Date: Mon, 12 Nov 2018 12:32:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 4.7.0 X-Bugzilla-Keywords: rejects-valid X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01017.txt.bz2 Content-length: 181 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D52869 --- Comment #9 from Jonathan Wakely --- Please send the patch to gcc-patches@gcc.gnu.org for review. >>From gcc-bugs-return-620861-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 13:06:04 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 44545 invoked by alias); 12 Nov 2018 13:06: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 44462 invoked by uid 48); 12 Nov 2018 13:05:59 -0000 From: "hubicka at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/87830] [9 Regression] ICE in cp_var_mod_type_p at cp/cp-objcp-common.c:107 since r265638 Date: Mon, 12 Nov 2018 13:06:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: lto X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: hubicka at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org X-Bugzilla-Target-Milestone: 9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01018.txt.bz2 Content-length: 840 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87830 Jan Hubicka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Jan Hubicka --- Fixed by: 2018-11-06 Jan Hubicka =20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20 * tree.c (free_lang_data): Reset overwite_assembler_name,=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 print_xnode, print_decl, print_type and print_identifier of=20=20= =20=20=20=20=20=20=20=20=20=20=20 langhooks. >>From gcc-bugs-return-620862-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 13:21:35 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 68687 invoked by alias); 12 Nov 2018 13:21: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 68624 invoked by uid 48); 12 Nov 2018 13:21:30 -0000 From: "iains at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/78444] Wrong prologue stack alignment for implicit dtor on x86_64-darwin* Date: Mon, 12 Nov 2018 13: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: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: iains at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01019.txt.bz2 Content-length: 1371 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D78444 --- Comment #9 from Iain Sandoe --- (In reply to Iain Sandoe from comment #8) > (In reply to Uro=C5=A1 Bizjak from comment #7) > > (In reply to Iain Sandoe from comment #6) > > > for sysV5 psABI targets, the call site requirement is 64 for m32 and = 126/256 > > > for m64. > > sysV5 requires 128bit alignment at the call site, but on linux no runti= me > > mechanism enforces this requirement. So, if it is possible to prove tha= t the > > called function doesn't need 128bit alignment, we can misalign the call= er to > > word size without consequences. From the trail of this PR, I suspect th= is is > > not the case on Darwin. >=20 > Correct; > Darwin's dynamic loader enforces the alignment requirement. The revised patch passes bootstrap, and the test case compiles [will reg-te= st on Darwin and Linux and then re-post]. NOTE: My understanding is that the intention of this ABI constraint is so t= hat the callee can make assumptions about stack alignment when using it for vec= tor items. The caller doesn't, in general, know whether the callee might use vectors -= and thus to some extent saying it's ok to break ABI if no-one catches you [ ;-)= ] is possibly not enough. Having said that, this seems to be a corner-case - this is the only time I'= ve seen it fire on Darwin. >>From gcc-bugs-return-620863-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 13:23:54 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 82395 invoked by alias); 12 Nov 2018 13:23: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 82159 invoked by uid 48); 12 Nov 2018 13:23:49 -0000 From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/87985] Compile-time and memory hog w/ -O1 -ftree-slp-vectorize Date: Mon, 12 Nov 2018 13:23:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 8.2.1 X-Bugzilla-Keywords: compile-time-hog, memory-hog X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01020.txt.bz2 Content-length: 848 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87985 --- Comment #3 from Richard Biener --- diff --git a/gcc/tree-data-ref.c b/gcc/tree-data-ref.c index 6019c6168bf..d60d389fa0a 100644 --- a/gcc/tree-data-ref.c +++ b/gcc/tree-data-ref.c @@ -682,7 +684,8 @@ split_constant_offset_1 (tree type, tree op0, enum tree_code code, tree op1, case SSA_NAME: { - if (SSA_NAME_OCCURS_IN_ABNORMAL_PHI (op0)) + if (SSA_NAME_OCCURS_IN_ABNORMAL_PHI (op0) + || !has_single_use (op0)) return false; gimple *def_stmt =3D SSA_NAME_DEF_STMT (op0); fixes this but that's very likely too restrictive. We are merely interested to limit multiple uses in the expression itself as we'd otherwise un-CSE those. A full-blown hash-map would do the trick here I guess. But at what expense? >>From gcc-bugs-return-620865-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 13:36:46 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 9308 invoked by alias); 12 Nov 2018 13:36: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 6687 invoked by uid 48); 12 Nov 2018 13:36:41 -0000 From: "mte.zych at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/87769] GCC build from source uses headers and libraries from directories host machine. Date: Mon, 12 Nov 2018 13:36: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: 9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mte.zych at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01022.txt.bz2 Content-length: 1292 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87769 Mateusz Zych changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|INVALID |--- --- Comment #5 from Mateusz Zych --- I read numerous articles describing how to build standalone GCC for source: - https://solarianprogrammer.com/2018/05/06/building-gcc-cross-compiler-raspb= erry-pi/ - https://preshing.com/20141119/how-to-build-a-gcc-cross-compiler/ - https://wiki.osdev.org/GCC_Cross-Compiler - https://wiki.osdev.org/Building_GCC - https://gist.github.com/maoueh/14ef25a03d5722bc1e03 None of above approaches worked for me. ;( I'm always ending up with some obscure compilation / linking issue. Can someone just explain to me, how to build GCC using configuration option "--with-sysroot=3D"? I would really appreciate it. PS. I am treating this as a bug, because I couldn't find any official documentation explaining how to build GCC using configuration option "--with-sysroot=3D". I just think that the whole process of doing so shouldn't be that hard. Thanks, Mateusz >>From gcc-bugs-return-620864-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 13:36:31 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 5739 invoked by alias); 12 Nov 2018 13:36: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 5344 invoked by uid 48); 12 Nov 2018 13:36:24 -0000 From: "ubizjak at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/78444] Wrong prologue stack alignment for implicit dtor on x86_64-darwin* Date: Mon, 12 Nov 2018 13:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 7.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: ubizjak 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: 2018-11/txt/msg01021.txt.bz2 Content-length: 627 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D78444 --- Comment #10 from Uro=C5=A1 Bizjak --- BTW: probably related to this PR, I have seen following kludge in i386/darwin.h: #define STACK_BOUNDARY \ ((profile_flag || TARGET_64BIT_MS_ABI) ? 128 : BITS_PER_WORD) It looks that profile_flag is there due to "call mcount" insn. However, crtl->profile is set in this case, and the vaule of the flag could be check= ed in the same place to eventually increase function alignment. Removing profile_flag would make Darwin's STACK_BOUNDARY definition the same as the default one, and could be removed. >>From gcc-bugs-return-620866-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 13:43:19 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 29178 invoked by alias); 12 Nov 2018 13:43: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 29087 invoked by uid 48); 12 Nov 2018 13:43:15 -0000 From: "iains at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/78444] Wrong prologue stack alignment for implicit dtor on x86_64-darwin* Date: Mon, 12 Nov 2018 13:43:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 7.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: iains at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01023.txt.bz2 Content-length: 925 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D78444 --- Comment #11 from Iain Sandoe --- (In reply to Uro=C5=A1 Bizjak from comment #10) > BTW: probably related to this PR, I have seen following kludge in > i386/darwin.h: >=20 > #define STACK_BOUNDARY \ > ((profile_flag || TARGET_64BIT_MS_ABI) ? 128 : BITS_PER_WORD) >=20 > It looks that profile_flag is there due to "call mcount" insn. However, > crtl->profile is set in this case, and the vaule of the flag could be > checked in the same place to eventually increase function alignment. > Removing profile_flag would make Darwin's STACK_BOUNDARY definition the s= ame > as the default one, and could be removed. I think you're correct - this was a case where a non-leaf use (the profile case) caused the dynamic loader to abort exes - and this hack is a work-aro= und. I will experiment with removing it when the proper check is in place. >>From gcc-bugs-return-620867-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 14:03:19 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 39188 invoked by alias); 12 Nov 2018 14:03: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 36109 invoked by uid 48); 12 Nov 2018 14:03:13 -0000 From: "clyon at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/81824] Warn for missing attributes with function aliases Date: Mon, 12 Nov 2018 14:03:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 7.0 X-Bugzilla-Keywords: diagnostic, patch X-Bugzilla-Severity: enhancement X-Bugzilla-Who: clyon at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org X-Bugzilla-Target-Milestone: 9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01024.txt.bz2 Content-length: 821 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81824 Christophe Lyon changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |clyon at gcc dot gnu.org --- Comment #12 from Christophe Lyon --- The new test gcc.dg/Wattribute-alias.c fails on bare-metal toolchains (eg arm-eabi, aarch64-elf): /gcc/testsuite/gcc.dg/Wattribute-alias.c:49:39: error: ifunc is not support= ed on this target /gcc/testsuite/gcc.dg/Wattribute-alias.c:48:44: error: ifunc is not support= ed on this target /gcc/testsuite/gcc.dg/Wattribute-alias.c:47:37: error: ifunc is not support= ed on this target I don't know if there is an effective-target for this? >>From gcc-bugs-return-620868-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 14:28:08 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 32891 invoked by alias); 12 Nov 2018 14:28: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 28885 invoked by uid 48); 12 Nov 2018 14:28:04 -0000 From: "sven.koehler at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/69502] attribute aligned reduces alignment contrary to documentation Date: Mon, 12 Nov 2018 14:28:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 6.0 X-Bugzilla-Keywords: documentation X-Bugzilla-Severity: normal X-Bugzilla-Who: sven.koehler at gmail dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01025.txt.bz2 Content-length: 748 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D69502 --- Comment #5 from Sven --- (In reply to sandra from comment #4) > Fixed on trunk. It's good thing that the documentation reflects the behavior of gcc.=20 But on the other hand, having the align attribute work in both directions i= s a bad idea, IMHO. Using an attribute to specify an alignment guarantee (setting a lower bound= on the actual alignment) is a benign thing. However, forcing lowering the alignment guarantee usually indicates some so= rt of "trickery" that may force the compiler to circumvent certain limitations= of the underlying platform. These two concepts (increasing alignment, lowering alignment) should be kept strictly separate. >>From gcc-bugs-return-620869-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 15:14:48 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 88424 invoked by alias); 12 Nov 2018 15:14: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 88368 invoked by uid 48); 12 Nov 2018 15:14:43 -0000 From: "wilco at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/87763] [9 Regression] aarch64 target testcases fail after r265398 Date: Mon, 12 Nov 2018 15:14:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rtl-optimization X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: wilco at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01026.txt.bz2 Content-length: 1556 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87763 Wilco changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wilco at gcc dot gnu.org --- Comment #3 from Wilco --- (In reply to Segher Boessenkool from comment #2) > The two relevant insns are >=20 > (insn 35 4 40 2 (set (reg:SI 33 v1 [99]) > (reg:SI 0 x0 [ a ])) "87763.c":2:1 46 {*movsi_aarch64} > (nil)) >=20 > (insn 7 10 8 2 (set (reg:SF 33 v1 [orig:95 c ] [95]) > (float:SF (reg:SI 33 v1 [99]))) "87763.c":2:14 921 {floatsisf2} > (nil)) >=20 > (this is the LRA dump; IRA already allocated those registers, LRA didn't > change anything). >=20 > 99 was assigned a floating point register: > Choosing alt 12 in insn 35: (0) w (1) rZ {*movsi_aarch64} > Choosing alt 0 in insn 7: (0) =3Dw (1) w {floatsisf2} >=20 > an integer register would be alt 0 (r<-r), resp. alt 1 (w<-?r). So > apparently > the "?" was costed as more strongly than the cost of the removable regist= er > move, or IRA didn't see that move was unnecessary. >=20 > Confirmed, btw. IRA costing doesn't consider the possibility of a simple move being removea= ble. Neither does it consider that some variants are more expensive than others - use of '?' is the only way to mark more expensive variants. The example shown is fixed when I change the w=3DrZ variant to ?w=3DrZ in movsi_aarch64. >>From gcc-bugs-return-620870-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 15:26:18 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 115963 invoked by alias); 12 Nov 2018 15:26: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 115862 invoked by uid 55); 12 Nov 2018 15:26:13 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/87963] libstdc++-v3/src/c++17/memory_resource.cc:515:31: error: static assertion failed for mingw-w64 target since r265853 Date: Mon, 12 Nov 2018 15:26:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: 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: 2018-11/txt/msg01027.txt.bz2 Content-length: 660 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87963 --- Comment #1 from Jonathan Wakely --- Author: redi Date: Mon Nov 12 15:25:40 2018 New Revision: 266032 URL: https://gcc.gnu.org/viewcvs?rev=3D266032&root=3Dgcc&view=3Drev Log: PR libstdc++/87963 fix build for 64-bit mingw PR libstdc++/87963 * src/c++17/memory_resource.cc (chunk::_M_bytes): Change type from unsigned to uint32_t. (chunk): Fix static assertion for 64-bit targets that aren't LP64. (bigblock::all_ones): Fix undefined shift. Modified: trunk/libstdc++-v3/ChangeLog trunk/libstdc++-v3/src/c++17/memory_resource.cc >>From gcc-bugs-return-620872-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 15:26:47 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 117427 invoked by alias); 12 Nov 2018 15:26: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 117361 invoked by uid 48); 12 Nov 2018 15:26:42 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/87963] libstdc++-v3/src/c++17/memory_resource.cc:515:31: error: static assertion failed for mingw-w64 target since r265853 Date: Mon, 12 Nov 2018 15:26:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: 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: 2018-11/txt/msg01029.txt.bz2 Content-length: 448 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87963 Jonathan Wakely changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Jonathan Wakely --- Should be fixed on trunk now. >>From gcc-bugs-return-620871-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 15:26:33 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 116682 invoked by alias); 12 Nov 2018 15:26: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 116634 invoked by uid 48); 12 Nov 2018 15:26:29 -0000 From: "lh_mouse at 126 dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/87987] New: Missed optimization with ranged-for loop on a constexpr array Date: Mon, 12 Nov 2018 15: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: 8.2.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: lh_mouse at 126 dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01028.txt.bz2 Content-length: 1698 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87987 Bug ID: 87987 Summary: Missed optimization with ranged-for loop on a constexpr array Product: gcc Version: 8.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: lh_mouse at 126 dot com Target Milestone: --- This simple program: ```c++ static constexpr bool table[] =3D { 1, 0, 0, 1, 1, 0, 1, 0 }; int check() { int sum =3D 0; for(auto value : table) { sum +=3D value; } return sum; } ``` after being compiled by GCC 8.2 with `-std=3Dc++11 -O2 -Wall -Wextra -Wpeda= ntic -Werror`, yields a loop: ```asm check(): mov edx, OFFSET FLAT:table xor eax, eax .L2: movzx ecx, BYTE PTR [rdx] add rdx, 1 add eax, ecx cmp rdx, OFFSET FLAT:table+8 jne .L2 ret ``` , while Clang 6.0 optimizes the body to a constant: ```asm check(): # @check() mov eax, 4 ret ``` ( Online comparison can be viewed here: https://gcc.godbolt.org/z/oaSr6j ) Making the function `constexpr` however overcomes this obstacle: ```c++ static constexpr bool table[] =3D { 1, 0, 0, 1, 1, 0, 1, 0 }; // This requires only C++11. constexpr int check_constexpr(const bool *p, int n) { return (n =3D=3D 0) ? 0 : *p + check_constexpr(p + 1, n - 1); } int check() { return check_constexpr(table, sizeof(table)); } ``` ( And here is the online comparison for this one: https://gcc.godbolt.org/z/HZjBSh ) >>From gcc-bugs-return-620873-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 15:31:06 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 9839 invoked by alias); 12 Nov 2018 15:31: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 9567 invoked by uid 48); 12 Nov 2018 15:31:00 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/87987] Missed optimization with ranged-for loop on a constexpr array Date: Mon, 12 Nov 2018 15:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 8.2.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on everconfirmed Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01030.txt.bz2 Content-length: 471 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87987 Jonathan Wakely changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |missed-optimization Status|UNCONFIRMED |NEW Last reconfirmed| |2018-11-12 Ever confirmed|0 |1 >>From gcc-bugs-return-620874-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 16:01:36 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 36988 invoked by alias); 12 Nov 2018 16:01: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 36836 invoked by uid 48); 12 Nov 2018 16:01:24 -0000 From: "hubicka at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/87988] New: [9 regression] Streaming of ABSTRACT_ORIGIN is expensive Date: Mon, 12 Nov 2018 16:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: lto X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hubicka 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: 2018-11/txt/msg01031.txt.bz2 Content-length: 4258 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87988 Bug ID: 87988 Summary: [9 regression] Streaming of ABSTRACT_ORIGIN is expensive Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: lto Assignee: unassigned at gcc dot gnu.org Reporter: hubicka at gcc dot gnu.org CC: marxin at gcc dot gnu.org Target Milestone: --- In GCC 9 we started to stream abstract origin everywhere. Disabling abstra= ct oririgin improves compile time->WPA streaming noticeably. For firefox: [WPA] read 14334905 SCCs of average size 1.322199=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 [WPA] 18953601 tree bodies read in total=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 [WPA] tree SCC table: size 4194301, 2934991 elements, collision ratio: 0.84= 8596=20 [WPA] tree SCC max chain length 156 (size 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 [WPA] Compared 5840684 SCCs, 3635813 collisions (0.622498)=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 [WPA] Merged 5823982 SCCs=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20 [WPA] Merged 9750701 tree bodies=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20 [WPA] Merged 3080308 types=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20 [WPA] 1618547 types prevailed (2296163 associated trees)=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 [WPA] GIMPLE canonical type table: size 32749, 22785 elements, 149714 searc= hes, 63531 collisions (ratio: 0.424349) [WPA] GIMPLE canonical type pointer-map: 22785 elements, 348267 searches=20= =20=20=20=20=20=20=20 [WPA] Compression: 297652239 input bytes, 898765275 uncompressed bytes (rat= io: 3.019515) [WPA] read 10675278 SCCs of average size 1.427853=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 [WPA] 15242724 tree bodies read in total=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 [WPA] tree SCC table: size 4194301, 1943675 elements, collision ratio: 0.78= 6758=20 [WPA] tree SCC max chain length 143 (size 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 [WPA] Compared 4140499 SCCs, 2713171 collisions (0.655276)=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 [WPA] Merged 4130159 SCCs=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20 [WPA] Merged 8014996 tree bodies=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20 [WPA] Merged 2381430 types=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20 [WPA] 1164716 types prevailed (1832970 associated trees)=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 [WPA] GIMPLE canonical type table: size 32749, 22769 elements, 141364 searc= hes, 63213 collisions (ratio: 0.447165) [WPA] GIMPLE canonical type pointer-map: 22769 elements, 346311 searches=20= =20=20=20=20=20=20=20 [WPA] Compression: 233507018 input bytes, 704808805 uncompressed bytes (rat= io: 3.018363) So roughly 27% of the decoded streams is attributed to abstract origins. GC memory use is 776MB comopared to 1014 and TOTAL GGC memory is 5537389 compa= red to 5028477 WPA->ltrans streaming is affected less 1.2GB compared to 1.3GB. >>From gcc-bugs-return-620875-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 16:02:38 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 39738 invoked by alias); 12 Nov 2018 16:02: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 39655 invoked by uid 48); 12 Nov 2018 16:02:34 -0000 From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/87977] [9 Regression] ICE: verify_ssa failed (error: definition in block 4 follows the use) Date: Mon, 12 Nov 2018 16:02:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org X-Bugzilla-Target-Milestone: 9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status 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: 2018-11/txt/msg01032.txt.bz2 Content-length: 578 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87977 Jakub Jelinek changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gn= u.org --- Comment #2 from Jakub Jelinek --- Created attachment 44988 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D44988&action=3Dedit gcc9-pr87977.patch Untested fix. >>From gcc-bugs-return-620876-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 16:06:32 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 21223 invoked by alias); 12 Nov 2018 16:06: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 11964 invoked by uid 48); 12 Nov 2018 16:06:25 -0000 From: "segher at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/87763] [9 Regression] aarch64 target testcases fail after r265398 Date: Mon, 12 Nov 2018 16:06:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rtl-optimization X-Bugzilla-Version: 9.0 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: 9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01033.txt.bz2 Content-length: 799 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87763 --- Comment #4 from Segher Boessenkool --- (In reply to Wilco from comment #3) > IRA costing doesn't consider the possibility of a simple move being > removeable. Not always, yeah (only if you have matching constraints, which are silly to have for moves; IRA or LRA should do the work, not the machine description). > Neither does it consider that some variants are more expensive > than others - use of '?' is the only way to mark more expensive variants. ? and !, or ^ and $ if it only more expensive if it needs reloads. > The example shown is fixed when I change the w=3DrZ variant to ?w=3DrZ in > movsi_aarch64. Is it always more expensive than the other alternatives? Then it *should* have "?" modifiers! >>From gcc-bugs-return-620877-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 16:08:17 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 103289 invoked by alias); 12 Nov 2018 16:08: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 103205 invoked by uid 48); 12 Nov 2018 16:08:13 -0000 From: "hubicka at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/86004] [9 regression] Several lto test cases begin failing with r260963 Date: Mon, 12 Nov 2018 16:08:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: lto X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: link-failure X-Bugzilla-Severity: normal X-Bugzilla-Who: hubicka at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01034.txt.bz2 Content-length: 274 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86004 --- Comment #9 from Jan Hubicka --- I wonder if we can close this based on fact that it only reproduces on sufficiently old binutils and we simply can't support incremental linking on these? >>From gcc-bugs-return-620878-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 16:41:21 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 91184 invoked by alias); 12 Nov 2018 16:41: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 90668 invoked by uid 48); 12 Nov 2018 16:41:16 -0000 From: "bergner at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/87899] [9 regression]r264897 cause mis-compiled native arm-linux-gnueabihf toolchain Date: Mon, 12 Nov 2018 16:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: bergner at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: bergner at gcc dot gnu.org X-Bugzilla-Target-Milestone: 9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status bug_file_loc cf_reconfirmed_on assigned_to everconfirmed Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01035.txt.bz2 Content-length: 699 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87899 Peter Bergner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED URL| |https://gcc.gnu.org/ml/gcc- | |patches/2018-11/msg00890.ht | |ml Last reconfirmed| |2018-11-12 Assignee|unassigned at gcc dot gnu.org |bergner at gcc dot = gnu.org Ever confirmed|0 |1 >>From gcc-bugs-return-620879-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 16:48:38 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 98125 invoked by alias); 12 Nov 2018 16:48: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 96225 invoked by uid 55); 12 Nov 2018 16:47:56 -0000 From: "renlin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/87815] ICE in DSE with -march=armv8-a+sve while trying to replace load with previously stored value Date: Mon, 12 Nov 2018 16:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: renlin at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: renlin at gcc dot gnu.org X-Bugzilla-Target-Milestone: 9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01036.txt.bz2 Content-length: 1059 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87815 --- Comment #1 from Renlin Li --- Author: renlin Date: Mon Nov 12 16:47:24 2018 New Revision: 266033 URL: https://gcc.gnu.org/viewcvs?rev=3D266033&root=3Dgcc&view=3Drev Log: [PR87815]Don't generate shift sequence for load replacement in DSE when the mode size is not compile-time constant The patch adds a check if the gap is compile-time constant. This happens when dse decides to replace the load with previous store value. The problem is that, shift sequence could not accept compile-time non-const= ant mode operand. gcc/ 2018-11-12 Renlin Li PR target/87815 * dse.c (get_stored_val): Add check for compile-time constantness of gap. gcc/testsuite/ 2018-11-12 Renlin Li PR target/87815 * gcc.target/aarch64/sve/pr87815.c: New. Added: trunk/gcc/testsuite/gcc.target/aarch64/sve/pr87815.c Modified: trunk/gcc/ChangeLog trunk/gcc/dse.c trunk/gcc/testsuite/ChangeLog >>From gcc-bugs-return-620880-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 16:49:13 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 98958 invoked by alias); 12 Nov 2018 16:48: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 98181 invoked by uid 48); 12 Nov 2018 16:48:34 -0000 From: "amonakov at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug inline-asm/87984] [7/8/9 Regression] wrong code for local reg var input to asm Date: Mon, 12 Nov 2018 16:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: inline-asm X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: amonakov at gcc dot gnu.org X-Bugzilla-Status: REOPENED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01037.txt.bz2 Content-length: 564 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87984 --- Comment #8 from Alexander Monakov --- Executable testcase suitable for bisecting, aborts with -O2 -m32 __attribute__((weak)) int f(long long x[]) { int o=3D0, i; for (i=3D0; i<3; i++) { register int a asm("eax"); a =3D x[0] / x[1]; asm("add %1, %0" : "+r"(o) : "r"(a)); asm("xor %%eax, %%eax" ::: "eax"); } return o; } int main() { long long x[] =3D {1, 1}; if (f(x) !=3D 3) __builtin_abort(); return 0; } >>From gcc-bugs-return-620881-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 16:50:16 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 100472 invoked by alias); 12 Nov 2018 16: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 100445 invoked by uid 48); 12 Nov 2018 16:50:12 -0000 From: "renlin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/87815] ICE in DSE with -march=armv8-a+sve while trying to replace load with previously stored value Date: Mon, 12 Nov 2018 16:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: renlin at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: renlin at gcc dot gnu.org X-Bugzilla-Target-Milestone: 9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01038.txt.bz2 Content-length: 425 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87815 Renlin Li changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Renlin Li --- Fix by r266033 >>From gcc-bugs-return-620882-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 16:51:46 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 102475 invoked by alias); 12 Nov 2018 16:51: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 102451 invoked by uid 48); 12 Nov 2018 16:51:42 -0000 From: "kretz at kde dot org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/87989] New: Calling operator T() invokes wrong conversion operator overload Date: Mon, 12 Nov 2018 16:51:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kretz at kde dot org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01039.txt.bz2 Content-length: 1012 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87989 Bug ID: 87989 Summary: Calling operator T() invokes wrong conversion operator overload Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: kretz at kde dot org Target Milestone: --- Testcase (https://godbolt.org/z/sStNGV): struct X { template operator T() const; operator float() const; }; template T f(const X &x) { return x.operator T(); } template float f(const X &); Starting with GCC8, this calls `X::operator float() const` instead of `X::operator float() const`. The behavior is correct if function f is chang= ed to `{ return x; }`; i.e. implicit call of the conversion operator. I have not double-checked the standard, but clang, EDG, MSVC and GCC <=3D 7= do not show this behavior. >>From gcc-bugs-return-620883-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 16:53:09 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 103846 invoked by alias); 12 Nov 2018 16:53: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 103820 invoked by uid 48); 12 Nov 2018 16:53:03 -0000 From: "kretz at kde dot org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/87989] Calling operator T() invokes wrong conversion operator overload Date: Mon, 12 Nov 2018 16:53:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kretz at kde dot org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: 2018-11/txt/msg01040.txt.bz2 Content-length: 441 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87989 Matthias Kretz changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |7.3.0 Known to fail| |8.1.0, 8.2.0 --- Comment #1 from Matthias Kretz --- might be related to #86521 >>From gcc-bugs-return-620884-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 16:53:25 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 104565 invoked by alias); 12 Nov 2018 16:53: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 104534 invoked by uid 48); 12 Nov 2018 16:53:21 -0000 From: "tomas.zencak at seznam dot cz" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/87990] New: using Base::operator= wrongly introduces user-declared move assignment operator Date: Mon, 12 Nov 2018 16:53:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tomas.zencak at seznam dot cz X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01041.txt.bz2 Content-length: 1435 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87990 Bug ID: 87990 Summary: using Base::operator=3D wrongly introduces user-declared move assignment operator Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: tomas.zencak at seznam dot cz Target Milestone: --- Created attachment 44989 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D44989&action=3Dedit Code failing to compile Compiling the attached code fails with the following error: testCompile.cpp:40:16: error: use of deleted function =E2=80=98world::world= (const world&)=E2=80=99 world copyww(w); ^ testCompile.cpp:11:8: note: =E2=80=98world::world(const world&)=E2=80=99 is= implicitly declared as deleted because =E2=80=98world=E2=80=99 declares a move constructor or m= ove assignment operator struct world: public hello Curiously enough, when the using declaration in class world2 is commented o= ut, the compilation succeeds and the program produces the expected results. IMO the code should compile, becuase the C++17 standard (N4659) 10.3.3.15 s= ays that declarations that would be hidden (which include copy/move assignment operator) are excluded from the set of declarations brought in by the using declaration. >>From gcc-bugs-return-620885-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 16:55:00 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 114560 invoked by alias); 12 Nov 2018 16:55: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 112125 invoked by uid 48); 12 Nov 2018 16:54:56 -0000 From: "tomas.zencak at seznam dot cz" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/87990] using Base::operator= wrongly introduces user-declared move assignment operator Date: Mon, 12 Nov 2018 16:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.3.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tomas.zencak at seznam dot cz X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc version Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01042.txt.bz2 Content-length: 581 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87990 Tom=C3=A1=C5=A1 =C5=BDen=C4=8D=C3=A1k chang= ed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tomas.zencak at seznam dot= cz Version|unknown |7.3.0 --- Comment #1 from Tom=C3=A1=C5=A1 =C5=BDen=C4=8D=C3=A1k --- The code also failed to compile on 9.0.0 as available at https://wandbox.or= g/ >>From gcc-bugs-return-620886-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 16:56:18 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 124113 invoked by alias); 12 Nov 2018 16:56: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 124049 invoked by uid 48); 12 Nov 2018 16:56:12 -0000 From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/87921] [7/8/9 Regression] Incorrect error "storage size of [array] isn't known (when it is) Date: Mon, 12 Nov 2018 16: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: unknown X-Bugzilla-Keywords: rejects-valid X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 7.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: 2018-11/txt/msg01043.txt.bz2 Content-length: 1474 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87921 Jakub Jelinek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org, | |jason at gcc dot gnu.org --- Comment #2 from Jakub Jelinek --- template struct X { static inline long x[] =3D { 1L }; long foo () { return x[0]; } }; void bar () { class L {}; X v {}; } reproduces it too. I think the problem is that we don't substitute for the inline static data members their initializers and call finish_static_data_member_decl with it. The comment says though: /* In [temp.inst]: [t]he initialization (and any associated side-effects) of a static data member does not occur unless the static data member is itself used in a way that requires the definition of the static data member to exist. Therefore, we do not substitute into the initialized for the static data member here. = */ and I can't find anything that would say that inline vars are to be treated differently. Jason? >>From gcc-bugs-return-620887-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 17:02:03 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 48842 invoked by alias); 12 Nov 2018 17:02: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 48727 invoked by uid 48); 12 Nov 2018 17:01:59 -0000 From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/87918] [9 Regression] ICE in simplify_binary_operation, at simplify-rtx.c:2153 since r264688 Date: Mon, 12 Nov 2018 17:02:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rtl-optimization X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01044.txt.bz2 Content-length: 569 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87918 Jakub Jelinek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #1 from Jakub Jelinek --- Testcases without using internals (__builtin_ia32_cmpless might go away): #include __m128 b, c, d; void foo (float f) { c =3D _mm_set_ss (f); d =3D _mm_cmple_ss (c, b); } >>From gcc-bugs-return-620888-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 17:14:52 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 7149 invoked by alias); 12 Nov 2018 17:14: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 7107 invoked by uid 48); 12 Nov 2018 17:14:47 -0000 From: "dominiq at lps dot ens.fr" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/87881] gfortran.dg/inquiry_type_ref_(1.f08|3.f90) fail on darwin Date: Mon, 12 Nov 2018 17:14:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: 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: 2018-11/txt/msg01045.txt.bz2 Content-length: 160 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87881 --- Comment #5 from Dominique d'Humieres --- Related to/duplicate of pr87945? >>From gcc-bugs-return-620889-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 17:16:29 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 8830 invoked by alias); 12 Nov 2018 17:16: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 8790 invoked by uid 48); 12 Nov 2018 17:16:22 -0000 From: "dominiq at lps dot ens.fr" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/87945] [9 Regression] ICE in var_element, at fortran/decl.c:281 Date: Mon, 12 Nov 2018 17:16:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: dominiq at lps dot ens.fr X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P4 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on everconfirmed Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01046.txt.bz2 Content-length: 614 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87945 Dominique d'Humieres changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ice-on-valid-code Status|UNCONFIRMED |NEW Last reconfirmed| |2018-11-12 Ever confirmed|0 |1 --- Comment #1 from Dominique d'Humieres --- Related to/duplicate of pr87881? IMO this is not a regression. >>From gcc-bugs-return-620890-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 17:23:02 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 29972 invoked by alias); 12 Nov 2018 17:23: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 29883 invoked by uid 48); 12 Nov 2018 17:22:58 -0000 From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/87918] [9 Regression] ICE in simplify_binary_operation, at simplify-rtx.c:2153 since r264688 Date: Mon, 12 Nov 2018 17:23:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rtl-optimization X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org X-Bugzilla-Target-Milestone: 9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on 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: 2018-11/txt/msg01047.txt.bz2 Content-length: 689 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87918 Jakub Jelinek changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed|2018-11-07 00:00:00 |2018-11-12 Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gn= u.org Ever confirmed|0 |1 --- Comment #2 from Jakub Jelinek --- Created attachment 44990 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D44990&action=3Dedit gcc9-pr87918.patch Untested fix. >>From gcc-bugs-return-620891-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 17:31:37 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 127582 invoked by alias); 12 Nov 2018 17:31: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 127497 invoked by uid 48); 12 Nov 2018 17:31:31 -0000 From: "wilco at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/87763] [9 Regression] aarch64 target testcases fail after r265398 Date: Mon, 12 Nov 2018 17:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rtl-optimization X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: wilco at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01048.txt.bz2 Content-length: 1267 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87763 --- Comment #5 from Wilco --- (In reply to Segher Boessenkool from comment #4) > (In reply to Wilco from comment #3) > > IRA costing doesn't consider the possibility of a simple move being > > removeable. >=20 > Not always, yeah (only if you have matching constraints, which are silly = to > have for moves; IRA or LRA should do the work, not the machine descriptio= n). Would it take this into account in the costs? I believe it doesn't. > > Neither does it consider that some variants are more expensive > > than others - use of '?' is the only way to mark more expensive variant= s. >=20 > ? and !, or ^ and $ if it only more expensive if it needs reloads. >=20 > > The example shown is fixed when I change the w=3DrZ variant to ?w=3DrZ = in > > movsi_aarch64. >=20 > Is it always more expensive than the other alternatives? Then it *should* > have "?" modifiers! Today using '?' seems to be the only way to tell it to prefer certain alternatives. However this is annoying given there are already separate cos= ts for moves between different register classes. So this means we end up hardcoding microarchitecture costs in the md files instead of using the existing cost hooks... >>From gcc-bugs-return-620892-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 17:44:47 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 18776 invoked by alias); 12 Nov 2018 17:44: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 18709 invoked by uid 48); 12 Nov 2018 17:44:41 -0000 From: "rearnsha at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/87763] [9 Regression] aarch64 target testcases fail after r265398 Date: Mon, 12 Nov 2018 17:44:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rtl-optimization X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rearnsha at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01049.txt.bz2 Content-length: 1609 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87763 --- Comment #6 from Richard Earnshaw --- (In reply to Wilco from comment #5) > (In reply to Segher Boessenkool from comment #4) > > (In reply to Wilco from comment #3) > > > IRA costing doesn't consider the possibility of a simple move being > > > removeable. > >=20 > > Not always, yeah (only if you have matching constraints, which are sill= y to > > have for moves; IRA or LRA should do the work, not the machine descript= ion). >=20 > Would it take this into account in the costs? I believe it doesn't. >=20 > > > Neither does it consider that some variants are more expensive > > > than others - use of '?' is the only way to mark more expensive varia= nts. > >=20 > > ? and !, or ^ and $ if it only more expensive if it needs reloads. > >=20 > > > The example shown is fixed when I change the w=3DrZ variant to ?w=3Dr= Z in > > > movsi_aarch64. > >=20 > > Is it always more expensive than the other alternatives? Then it *shou= ld* > > have "?" modifiers! >=20 > Today using '?' seems to be the only way to tell it to prefer certain > alternatives. However this is annoying given there are already separate > costs for moves between different register classes. So this means we end = up > hardcoding microarchitecture costs in the md files instead of using the > existing cost hooks... The '?' modifiers approach is not really suitable for any case where the co= st might depend on the micro-architecture. There's only one cost that can be applied this way, and if it doesn't suit all implementations, you're hosed. >>From gcc-bugs-return-620893-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 17:55:42 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 87022 invoked by alias); 12 Nov 2018 17:55:42 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 85686 invoked by uid 48); 12 Nov 2018 17:55:36 -0000 From: "dominiq at lps dot ens.fr" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/68717] [7/8/9 Regression] New (bogus?) warnings when compiling some gfortran.dg tests with -flto after r231239 Date: Mon, 12 Nov 2018 17:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 6.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: dominiq at lps dot ens.fr X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P4 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 7.4 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01050.txt.bz2 Content-length: 414 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D68717 --- Comment #10 from Dominique d'Humieres --- The warnings are gone between revisions r265814 and r265942. =46rom comment 1 > As discussed in the other related PR, those are real issues -=20 > Fortran frontend should not declare one function with multiple > and incompatible declarations. this looks like a regression, isn't it? >>From gcc-bugs-return-620894-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 17:55:57 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 88008 invoked by alias); 12 Nov 2018 17:55: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 87808 invoked by uid 48); 12 Nov 2018 17:55:52 -0000 From: "gscfq@t-online.de" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/78492] [OOP] Compiler segfault with non_overridable function in generic interface Date: Mon, 12 Nov 2018 17:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 6.1.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: gscfq@t-online.de X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P4 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01051.txt.bz2 Content-length: 1925 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D78492 G. Steinmetz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gscfq@t-online.de --- Comment #4 from G. Steinmetz --- Update with a simplification : $ cat z1.f90 module m type t contains procedure, non_overridable :: g generic :: f =3D> g end type contains recursive function g(x) class(t), intent(in) :: x print *, x%f() end end $ gfortran-9-20181111 -c z1.f90 z1.f90:10:0: 10 | print *, x%f() | internal compiler error: in conv_function_val, at fortran/trans-expr.c:3810 0x6f95e0 conv_function_val ../../gcc/fortran/trans-expr.c:3809 0x6f95e0 gfc_conv_procedure_call(gfc_se*, gfc_symbol*, gfc_actual_arglist*, gfc_expr*, vec*) ../../gcc/fortran/trans-expr.c:6300 0x6fa29c gfc_conv_function_expr ../../gcc/fortran/trans-expr.c:6928 0x6ee90a gfc_conv_expr(gfc_se*, gfc_expr*) ../../gcc/fortran/trans-expr.c:8039 0x6f43b5 gfc_conv_expr_reference(gfc_se*, gfc_expr*, bool) ../../gcc/fortran/trans-expr.c:8184 0x71b007 gfc_trans_transfer(gfc_code*) ../../gcc/fortran/trans-io.c:2584 0x6c0067 trans_code ../../gcc/fortran/trans.c:2038 0x718afe build_dt ../../gcc/fortran/trans-io.c:2026 0x6c0047 trans_code ../../gcc/fortran/trans.c:2010 0x6e7674 gfc_generate_function_code(gfc_namespace*) ../../gcc/fortran/trans-decl.c:6509 0x6c3b39 gfc_generate_module_code(gfc_namespace*) ../../gcc/fortran/trans.c:2216 0x67440b translate_all_program_units ../../gcc/fortran/parse.c:6112 0x67440b gfc_parse_file() ../../gcc/fortran/parse.c:6328 0x6bc89f gfc_be_parse_file ../../gcc/fortran/f95-lang.c:204 >>From gcc-bugs-return-620895-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 17:57:19 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 95788 invoked by alias); 12 Nov 2018 17:57: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 95705 invoked by uid 48); 12 Nov 2018 17:57:15 -0000 From: "dominiq at lps dot ens.fr" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/68649] [7/8/9 Regression] note: code may be misoptimized unless -fno-strict-aliasing is used Date: Mon, 12 Nov 2018 17:57:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 6.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: dominiq at lps dot ens.fr X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P4 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 7.4 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01052.txt.bz2 Content-length: 189 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D68649 --- Comment #24 from Dominique d'Humieres --- The warnings are gone between revisions r265814 and r265942. >>From gcc-bugs-return-620896-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 17:58:04 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 96820 invoked by alias); 12 Nov 2018 17:58: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 96675 invoked by uid 48); 12 Nov 2018 17:57:58 -0000 From: "wilco at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/87763] [9 Regression] aarch64 target testcases fail after r265398 Date: Mon, 12 Nov 2018 17:58:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rtl-optimization X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: wilco at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01053.txt.bz2 Content-length: 1869 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87763 --- Comment #7 from Wilco --- (In reply to Richard Earnshaw from comment #6) > (In reply to Wilco from comment #5) > > (In reply to Segher Boessenkool from comment #4) > > > (In reply to Wilco from comment #3) > > > > IRA costing doesn't consider the possibility of a simple move being > > > > removeable. > > >=20 > > > Not always, yeah (only if you have matching constraints, which are si= lly to > > > have for moves; IRA or LRA should do the work, not the machine descri= ption). > >=20 > > Would it take this into account in the costs? I believe it doesn't. > >=20 > > > > Neither does it consider that some variants are more expensive > > > > than others - use of '?' is the only way to mark more expensive var= iants. > > >=20 > > > ? and !, or ^ and $ if it only more expensive if it needs reloads. > > >=20 > > > > The example shown is fixed when I change the w=3DrZ variant to ?w= =3DrZ in > > > > movsi_aarch64. > > >=20 > > > Is it always more expensive than the other alternatives? Then it *sh= ould* > > > have "?" modifiers! > >=20 > > Today using '?' seems to be the only way to tell it to prefer certain > > alternatives. However this is annoying given there are already separate > > costs for moves between different register classes. So this means we en= d up > > hardcoding microarchitecture costs in the md files instead of using the > > existing cost hooks... >=20 > The '?' modifiers approach is not really suitable for any case where the > cost might depend on the micro-architecture. There's only one cost that = can > be applied this way, and if it doesn't suit all implementations, you're > hosed. Yes all you can say "this is slightly more expensive". Anyway if it solves most/all the test failures then at least we're getting back to where we sho= uld be. >>From gcc-bugs-return-620897-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 17:59:03 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 108071 invoked by alias); 12 Nov 2018 17:59: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 105731 invoked by uid 48); 12 Nov 2018 17:58:59 -0000 From: "msebor at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug web/79738] Documentation for __attribute__((const)) slightly misleading Date: Mon, 12 Nov 2018 17:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: web X-Bugzilla-Version: 7.0 X-Bugzilla-Keywords: documentation X-Bugzilla-Severity: normal X-Bugzilla-Who: msebor at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01054.txt.bz2 Content-length: 242 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D79738 --- Comment #3 from Martin Sebor --- Correct: r255469 didn't change the semantics of either of the two attributes (it just rejects declarations that use both). >>From gcc-bugs-return-620898-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 18:00:37 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 112244 invoked by alias); 12 Nov 2018 18:00: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 111870 invoked by uid 48); 12 Nov 2018 18:00:00 -0000 From: "gscfq@t-online.de" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/87991] New: ICE in gfc_constructor_append_expr, at fortran/constructor.c:135 Date: Mon, 12 Nov 2018 18:00:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gscfq@t-online.de X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01055.txt.bz2 Content-length: 1657 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87991 Bug ID: 87991 Summary: ICE in gfc_constructor_append_expr, at fortran/constructor.c:135 Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- With (presumably) invalid code down to at least gfortran-5 : $ cat z1.f90 program p type t character(:), pointer :: c end type type(t) :: x allocate (character(3) :: x%c) data x%c /'abc'/ end $ cat z2.f90 module m type t character(:), pointer :: c end type end program p use m type(t) :: x allocate (character(3) :: x%c) data x%c /'abc'/ end $ gfortran-9-20181111 -c z1.f90 f951: internal compiler error: Segmentation fault 0xb297bf crash_signal ../../gcc/toplev.c:325 0x5fea1b gfc_constructor_append_expr(splay_tree_s**, gfc_expr*, locus*) ../../gcc/fortran/constructor.c:135 0x60067c formalize_structure_cons ../../gcc/fortran/data.c:645 0x60067c formalize_init_expr ../../gcc/fortran/data.c:682 0x6aa142 do_traverse_symtree ../../gcc/fortran/symbol.c:4151 0x681833 resolve_types ../../gcc/fortran/resolve.c:16647 0x68656c gfc_resolve(gfc_namespace*) ../../gcc/fortran/resolve.c:16733 0x674337 resolve_all_program_units ../../gcc/fortran/parse.c:6064 0x674337 gfc_parse_file() ../../gcc/fortran/parse.c:6314 0x6bc89f gfc_be_parse_file ../../gcc/fortran/f95-lang.c:204 >>From gcc-bugs-return-620900-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 18:03:38 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 118414 invoked by alias); 12 Nov 2018 18:03: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 118239 invoked by uid 48); 12 Nov 2018 18:03:31 -0000 From: "gscfq@t-online.de" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/87992] New: ICE in resolve_fl_variable, at fortran/resolve.c:12314 Date: Mon, 12 Nov 2018 18:03:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gscfq@t-online.de X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01057.txt.bz2 Content-length: 1336 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87992 Bug ID: 87992 Summary: ICE in resolve_fl_variable, at fortran/resolve.c:12314 Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Changed between 20180909 and 20180916 : $ cat z1.f90 subroutine s(x) class(*), allocatable :: x x =3D '' end $ gfortran-9-20180909 -c z1.f90 $ $ gfortran-9-20181111 -c z1.f90 f951: internal compiler error: Segmentation fault 0xb297bf crash_signal ../../gcc/toplev.c:325 0x68947c resolve_fl_variable ../../gcc/fortran/resolve.c:12314 0x68947c resolve_symbol ../../gcc/fortran/resolve.c:15293 0x6aa142 do_traverse_symtree ../../gcc/fortran/symbol.c:4151 0x681634 resolve_types ../../gcc/fortran/resolve.c:16619 0x681740 resolve_types ../../gcc/fortran/resolve.c:16630 0x68656c gfc_resolve(gfc_namespace*) ../../gcc/fortran/resolve.c:16733 0x674337 resolve_all_program_units ../../gcc/fortran/parse.c:6064 0x674337 gfc_parse_file() ../../gcc/fortran/parse.c:6314 0x6bc89f gfc_be_parse_file ../../gcc/fortran/f95-lang.c:204 >>From gcc-bugs-return-620901-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 18:03:39 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 118560 invoked by alias); 12 Nov 2018 18:03: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 118318 invoked by uid 48); 12 Nov 2018 18:03:34 -0000 From: "msebor at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/81824] Warn for missing attributes with function aliases Date: Mon, 12 Nov 2018 18:03:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 7.0 X-Bugzilla-Keywords: diagnostic, patch X-Bugzilla-Severity: enhancement X-Bugzilla-Who: msebor at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org X-Bugzilla-Target-Milestone: 9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01058.txt.bz2 Content-length: 163 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81824 --- Comment #14 from Martin Sebor --- Thanks. The test needed dg-require-ifunc. >>From gcc-bugs-return-620899-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 18:03:19 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 116711 invoked by alias); 12 Nov 2018 18:03: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 116516 invoked by uid 55); 12 Nov 2018 18:03:13 -0000 From: "msebor at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/81824] Warn for missing attributes with function aliases Date: Mon, 12 Nov 2018 18:03:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 7.0 X-Bugzilla-Keywords: diagnostic, patch X-Bugzilla-Severity: enhancement X-Bugzilla-Who: msebor at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org X-Bugzilla-Target-Milestone: 9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01056.txt.bz2 Content-length: 506 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81824 --- Comment #13 from Martin Sebor --- Author: msebor Date: Mon Nov 12 18:02:41 2018 New Revision: 266034 URL: https://gcc.gnu.org/viewcvs?rev=3D266034&root=3Dgcc&view=3Drev Log: PR c/81824 - Warn for missing attributes with function aliases gcc/testsuite/ChangeLog: * gcc.dg/Wattribute-alias.c: Require ifunc support. Modified: trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gcc.dg/Wattribute-alias.c >>From gcc-bugs-return-620902-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 18:08:19 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 125127 invoked by alias); 12 Nov 2018 18:08: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 125050 invoked by uid 48); 12 Nov 2018 18:08:15 -0000 From: "msebor at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/86004] [9 regression] Several lto test cases begin failing with r260963 Date: Mon, 12 Nov 2018 18:08:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: lto X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: link-failure X-Bugzilla-Severity: normal X-Bugzilla-Who: msebor at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01059.txt.bz2 Content-length: 441 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86004 --- Comment #10 from Martin Sebor --- Both of our (Red Hat internal) build servers have been upgraded to Fedora 2= 9 so we don't see the failures anymore but they will still com up on systems with older Binutils. Is it possible to add some sort of a dg-require-xxx to prevent the tests from failing when the installed version of Binutils isn't= up to par? >>From gcc-bugs-return-620903-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 18:13:36 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 128904 invoked by alias); 12 Nov 2018 18:13: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 128827 invoked by uid 48); 12 Nov 2018 18:13:29 -0000 From: "segher at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/85925] [7/8/9 regression] Mis-compilation at -02, masking with 257 goes wrong in combine Date: Mon, 12 Nov 2018 18:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rtl-optimization X-Bugzilla-Version: 8.1.1 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: segher at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org X-Bugzilla-Target-Milestone: 7.4 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01060.txt.bz2 Content-length: 821 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D85925 --- Comment #13 from Segher Boessenkool --- Sorry, I forgot. Here is the correct data: alpha 100.834%=20=20 arm 100.040%=20=20 c6x 100.000%=20=20 csky 100.039%=20=20 h8300 100.000%=20=20 i386 100.000%=20=20 microblaze 100.000%=20=20 mips 100.000%=20=20 mips64 100.029%=20=20 nios2 100.000%=20=20 parisc 100.025%=20=20 parisc64 100.017%=20=20 powerpc64 100.000%=20=20 riscv64 100.034%=20=20 s390 100.000%=20=20 sh 100.006%=20=20 shnommu 100.002%=20=20 sparc 100.001%=20=20 sparc64 100.001%=20=20 x86_64 100.000% (so pretty much the same, but the previous runs had some weird pollution). >>From gcc-bugs-return-620904-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 18:19:14 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 85538 invoked by alias); 12 Nov 2018 18:19: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 85492 invoked by uid 48); 12 Nov 2018 18:19:09 -0000 From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/87859] [8/9 Regression] store-merging miscompilation of mesa Date: Mon, 12 Nov 2018 18:19:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.3 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01061.txt.bz2 Content-length: 724 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87859 --- Comment #10 from Jakub Jelinek --- Created attachment 44991 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D44991&action=3Dedit gcc9-pr87859.patch This is the approach I had my mind. For *_24.c it makes no difference, but= for *_25.c, instead of: New sequence of 2 stores to replace old one of 14 stores New sequence of 1 stores to replace old one of 6 stores it now emits: New sequence of 1 stores to replace old one of 8 stores New sequence of 2 stores to replace old one of 10 stores New sequence of 1 stores to replace old one of 6 stores Resulting assembly is one insn larger. So, something that would need to be analyzed. >>From gcc-bugs-return-620905-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 18:55:50 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 3860 invoked by alias); 12 Nov 2018 18: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 125833 invoked by uid 48); 12 Nov 2018 18:55:44 -0000 From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/87859] store-merging miscompilation of mesa Date: Mon, 12 Nov 2018 18:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.3 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: 2018-11/txt/msg01062.txt.bz2 Content-length: 531 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87859 Jakub Jelinek changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[8/9 Regression] |store-merging |store-merging |miscompilation of mesa |miscompilation of mesa | --- Comment #11 from Jakub Jelinek --- In any case, the regression is fixed now. >>From gcc-bugs-return-620906-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 19:09:14 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 5203 invoked by alias); 12 Nov 2018 19:09: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 5155 invoked by uid 55); 12 Nov 2018 19:09:10 -0000 From: "sandra at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/21110] incorrect documentat for high and lo_sum RTL operators Date: Mon, 12 Nov 2018 19:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 4.1.0 X-Bugzilla-Keywords: documentation X-Bugzilla-Severity: normal X-Bugzilla-Who: sandra at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01063.txt.bz2 Content-length: 549 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D21110 --- Comment #3 from sandra at gcc dot gnu.org --- Author: sandra Date: Mon Nov 12 19:08:37 2018 New Revision: 266035 URL: https://gcc.gnu.org/viewcvs?rev=3D266035&root=3Dgcc&view=3Drev Log: 2018-11-12 Sandra Loosemore PR middle-end/21110 gcc/ * doc/rtl.texi (Constants): Clarify that mode of "high" doesn't have to be Pmode. (Arithmetic): Likewise for "lo_sum". Modified: trunk/gcc/ChangeLog trunk/gcc/doc/rtl.texi >>From gcc-bugs-return-620907-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 19:13:26 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 38044 invoked by alias); 12 Nov 2018 19:13: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 37916 invoked by uid 48); 12 Nov 2018 19:13:20 -0000 From: "sandra at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/21110] incorrect documentat for high and lo_sum RTL operators Date: Mon, 12 Nov 2018 19:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 4.1.0 X-Bugzilla-Keywords: documentation X-Bugzilla-Severity: normal X-Bugzilla-Who: sandra at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: 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: 2018-11/txt/msg01064.txt.bz2 Content-length: 477 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D21110 sandra at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |sandra at gcc dot gnu.org Resolution|--- |FIXED --- Comment #4 from sandra at gcc dot gnu.org --- Fixed on trunk. >>From gcc-bugs-return-620908-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 19:18:12 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 48842 invoked by alias); 12 Nov 2018 19:18: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 48758 invoked by uid 48); 12 Nov 2018 19:18:06 -0000 From: "gary_mills at fastmail dot fm" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/87836] ICE in cc1 for gcc-6.5.0 with SPARC hardware Date: Mon, 12 Nov 2018 19:18:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 7.3.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gary_mills at fastmail dot fm 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: 2018-11/txt/msg01065.txt.bz2 Content-length: 3620 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87836 --- Comment #10 from Gary Mills --- Thanks for the explanation. It's entirely possible that the intermediate g= cc was miss-compiled because of excessive optimization. I tried building gcc-7.3.0 with -O1 for 32-bit SPARC only, and got the same ICE. Here's part of build/sparcv7/sparc-sun-solaris2.11/libgcc/config.log: configure:3662: checking for suffix of object files configure:3684: /export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/bu= ild/sparcv7/./gcc/xgcc -B/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/= build/sparcv7/./gcc/ -B/usr/gcc/7/sparc-sun-solaris2.11/bin/ -B/usr/gcc/7/sparc-sun-solaris2.11/= lib/ -isystem /usr/gcc/7/sparc-sun-solaris2.11/include -isystem /usr/gcc/7/sparc-sun-solaris2.11/sys-include -c -O2 -g -O1 conftest.c >= &5 conftest.c: In function 'main': conftest.c:11:1: internal compiler error: Segmentation Fault main () ^~~~ 0x68930f crash_signal =20=20=20=20=20=20=20 /export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gc= c-7.3.0/gcc/toplev.c:337 0x399380 et_splay =20=20=20=20=20=20=20 /export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gc= c-7.3.0/gcc/et-forest.c:312 0x39a06b et_set_father =20=20=20=20=20=20=20 /export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gc= c-7.3.0/gcc/et-forest.c:526 0x32f4b7 calculate_dominance_info(cdi_direction) =20=20=20=20=20=20=20 /export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gc= c-7.3.0/gcc/dominance.c:739 0x6cb28b cleanup_tree_cfg_noloop =20=20=20=20=20=20=20 /export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gc= c-7.3.0/gcc/tree-cfgcleanup.c:766 0x6cb28b cleanup_tree_cfg() =20=20=20=20=20=20=20 /export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gc= c-7.3.0/gcc/tree-cfgcleanup.c:883 0x6c58af execute_build_cfg =20=20=20=20=20=20=20 /export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gc= c-7.3.0/gcc/tree-cfg.c:404 0x6c58af execute =20=20=20=20=20=20=20 /export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gc= c-7.3.0/gcc/tree-cfg.c:433 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See for instructions. configure:3688: $? =3D 1 configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "GNU C Runtime Library" | #define PACKAGE_TARNAME "libgcc" | #define PACKAGE_VERSION "1.0" | #define PACKAGE_STRING "GNU C Runtime Library 1.0" | #define PACKAGE_BUGREPORT "" | #define PACKAGE_URL "http://www.gnu.org/software/libgcc/" | /* end confdefs.h. */ |=20 | int | main () | { |=20 | ; | return 0; | } configure:3702: error: in `/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/b= uild/sparcv7/sparc-sun-solaris2.11/libgcc': configure:3705: error: cannot compute suffix of object files: cannot compile I had hoped that a reduction from -O2 to -O1 would be sufficient, but it mu= st not have been. The curious thing was that two copies of xgcc were created during the build: $ find build -name xgcc -ls=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 23236147 5382 -rwxr-xr-x 1 mills staff 5436884 Nov 11 21:10 build/sparcv7/gcc/xgcc 23217408 4870 -rwxr-xr-x 1 mills staff 4929308 Nov 10 15:19 build/sparcv7/prev-gcc/xgcc I'll try the build again with -O0 to see what happens then. >>From gcc-bugs-return-620909-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 19:25:30 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 94219 invoked by alias); 12 Nov 2018 19:25: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 94207 invoked by uid 48); 12 Nov 2018 19:25:25 -0000 From: "gscfq@t-online.de" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/87945] [9 Regression] ICE in var_element, at fortran/decl.c:281 Date: Mon, 12 Nov 2018 19:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: gscfq@t-online.de X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P4 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01066.txt.bz2 Content-length: 523 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87945 --- Comment #2 from G. Steinmetz --- z1.90 above should be _invalid_ code, because a type parameter inquiry can never be assigned a value, and should not be on LHS. An aequivalent example : $ cat z4.f90 program p character :: a, b a%len =3D 1 b%kind =3D 'b' ! plus type mismatch end Both examples from pr87881 comment 2 are looking good with their legal inquiries. Tested with latest official snapshot, no additonal patches applied. >>From gcc-bugs-return-620910-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 19:27:39 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 99158 invoked by alias); 12 Nov 2018 19:27: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 98906 invoked by uid 48); 12 Nov 2018 19:27:31 -0000 From: "gscfq@t-online.de" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/87993] New: ICE in gfc_constructor_first, at fortran/constructor.c:234 Date: Mon, 12 Nov 2018 19:27:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gscfq@t-online.de X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01067.txt.bz2 Content-length: 2272 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87993 Bug ID: 87993 Summary: ICE in gfc_constructor_first, at fortran/constructor.c:234 Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Should be valid code, according to F2018 9.4.5 a type-param-inquiry is scalar even if the designator is an array. $ cat z1.f90 program p integer, parameter :: a(2) =3D 1 integer, parameter :: b =3D a(2)%kind end $ cat z2.f90 program p integer, parameter :: a(2) =3D 1 integer, parameter :: b =3D a%kind end $ gfortran-9-20181111 -c z1.f90 f951: internal compiler error: Segmentation fault 0xb297bf crash_signal ../../gcc/toplev.c:325 0x1372630 splay_tree_min ../../libiberty/splay-tree.c:487 0x5feb8d gfc_constructor_first(splay_tree_s*) ../../gcc/fortran/constructor.c:234 0x61ed48 simplify_constructor ../../gcc/fortran/expr.c:1240 0x61ed48 gfc_simplify_expr(gfc_expr*, int) ../../gcc/fortran/expr.c:2174 0x61f16c simplify_parameter_variable ../../gcc/fortran/expr.c:2016 0x61ef79 gfc_simplify_expr(gfc_expr*, int) ../../gcc/fortran/expr.c:2153 0x678059 gfc_match_varspec(gfc_expr*, int, bool, bool) ../../gcc/fortran/primary.c:2287 0x679b6e gfc_match_rvalue(gfc_expr**) ../../gcc/fortran/primary.c:3429 0x6503ee match_primary ../../gcc/fortran/matchexp.c:157 0x6503ee match_level_1 ../../gcc/fortran/matchexp.c:211 0x6503ee match_mult_operand ../../gcc/fortran/matchexp.c:267 0x650638 match_add_operand ../../gcc/fortran/matchexp.c:356 0x65088c match_level_2 ../../gcc/fortran/matchexp.c:480 0x6509e2 match_level_3 ../../gcc/fortran/matchexp.c:551 0x650ad4 match_level_4 ../../gcc/fortran/matchexp.c:599 0x650ad4 match_and_operand ../../gcc/fortran/matchexp.c:693 0x650cc2 match_or_operand ../../gcc/fortran/matchexp.c:722 0x650d92 match_equiv_operand ../../gcc/fortran/matchexp.c:765 0x650e64 match_level_5 ../../gcc/fortran/matchexp.c:811 >>From gcc-bugs-return-620911-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 19:36:38 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 119249 invoked by alias); 12 Nov 2018 19:36: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 119196 invoked by uid 48); 12 Nov 2018 19:36:33 -0000 From: "gscfq@t-online.de" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/87994] New: ICE in match_data_constant, at fortran/decl.c:399 Date: Mon, 12 Nov 2018 19:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gscfq@t-online.de X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01068.txt.bz2 Content-length: 1362 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87994 Bug ID: 87994 Summary: ICE in match_data_constant, at fortran/decl.c:399 Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Should be valid code, thematically related to pr87993. $ cat z1.f90 program p real :: a, b data b /a%kind/ end $ gfortran-9-20181111 -c z1.f90 f951: internal compiler error: Segmentation fault 0xb297bf crash_signal ../../gcc/toplev.c:325 0x604ded match_data_constant ../../gcc/fortran/decl.c:399 0x604f83 top_val_list ../../gcc/fortran/decl.c:472 0x60519f gfc_match_data() ../../gcc/fortran/decl.c:616 0x66a7f1 match_word ../../gcc/fortran/parse.c:65 0x66df36 decode_statement ../../gcc/fortran/parse.c:468 0x66eb5a next_free ../../gcc/fortran/parse.c:1234 0x66eb5a next_statement ../../gcc/fortran/parse.c:1466 0x67016b parse_spec ../../gcc/fortran/parse.c:3858 0x672c37 parse_progunit ../../gcc/fortran/parse.c:5671 0x6742b9 gfc_parse_file() ../../gcc/fortran/parse.c:6211 0x6bc89f gfc_be_parse_file ../../gcc/fortran/f95-lang.c:204 >>From gcc-bugs-return-620912-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 19:42:58 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 123700 invoked by alias); 12 Nov 2018 19:42: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 123422 invoked by uid 48); 12 Nov 2018 19:42:53 -0000 From: "seurer at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/87995] New: [9 regression] libgomp.c/../libgomp.c-c++-common/cancel-taskgroup-3.c fails consistently after r265930 Date: Mon, 12 Nov 2018 19:42: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: 9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: seurer at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter 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: 2018-11/txt/msg01069.txt.bz2 Content-length: 5046 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87995 Bug ID: 87995 Summary: [9 regression] libgomp.c/../libgomp.c-c++-common/cancel-taskgroup-3.c fails consistently after r265930 Product: gcc Version: 9.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: --- I think I have seen this test case fail on rare occasions before but starti= ng with r265930 it now fails consistently on powerpc64 and powepc64le both on power 8 and power 9. Looking at the test logs posted on gcc-testresults it appears to be failing on x86, aarch64, and others starting at about the same time. spawn -ignore SIGHUP /home/seurer/gcc/build/gcc-test2/gcc/xgcc -B/home/seurer/gcc/build/gcc-test2/gcc/ /home/seurer/gcc/gcc-test2/libgomp/testsuite/libgomp.c/../libgomp.c-c++-com= mon/cancel-taskgroup-3.c -B/home/seurer/gcc/build/gcc-test2/powerpc64-unknown-linux-gnu/./libgomp/ -B/home/seurer/gcc/build/gcc-test2/powerpc64-unknown-linux-gnu/./libgomp/.l= ibs -I/home/seurer/gcc/build/gcc-test2/powerpc64-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 -= O2 -L/home/seurer/gcc/build/gcc-test2/powerpc64-unknown-linux-gnu/./libgomp/.l= ibs -lm -o ./cancel-taskgroup-3.exe PASS: libgomp.c/../libgomp.c-c++-common/cancel-taskgroup-3.c (test for exce= ss errors) Setting LD_LIBRARY_PATH to .:/home/seurer/gcc/build/gcc-test2/powerpc64-unknown-linux-gnu/./libgomp/.l= ibs:/home/seurer/gcc/build/gcc-test2/gcc:.:/home/seurer/gcc/build/gcc-test2= /powerpc64-unknown-linux-gnu/./libgomp/.libs:/home/seurer/gcc/build/gcc-tes= t2/gcc:/home/seurer/gcc/build/gcc-test2/./gmp/.libs:/home/seurer/gcc/build/= gcc-test2/./prev-gmp/.libs:/home/seurer/gcc/build/gcc-test2/./mpfr/src/.lib= s:/home/seurer/gcc/build/gcc-test2/./prev-mpfr/src/.libs:/home/seurer/gcc/b= uild/gcc-test2/./mpc/src/.libs:/home/seurer/gcc/build/gcc-test2/./prev-mpc/= src/.libs:/home/seurer/gcc/build/gcc-test2/./isl/.libs:/home/seurer/gcc/bui= ld/gcc-test2/./prev-isl/.libs:/home/seurer/gcc/install/gcc-7.2.0/lib64 Execution timeout is: 300 spawn [open ...] FAIL: libgomp.c/../libgomp.c-c++-common/cancel-taskgroup-3.c execution test spawn -ignore SIGHUP /home/seurer/gcc/build/gcc-test2/gcc/xgcc -B/home/seurer/gcc/build/gcc-test2/gcc/ -x c++ /home/seurer/gcc/gcc-test2/libgomp/testsuite/libgomp.c++/../libgomp.c-c++-c= ommon/cancel-taskgroup-3.c -B/home/seurer/gcc/build/gcc-test2/powerpc64-unknown-linux-gnu/./libgomp/ -B/home/seurer/gcc/build/gcc-test2/powerpc64-unknown-linux-gnu/./libgomp/.l= ibs -I/home/seurer/gcc/build/gcc-test2/powerpc64-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 -nostdinc++ -I/home/seurer/gcc/build/gcc-test2/powerpc64-unknown-linux-gnu/libstdc++-v3= /include/powerpc64-unknown-linux-gnu -I/home/seurer/gcc/build/gcc-test2/powerpc64-unknown-linux-gnu/libstdc++-v3= /include -I/home/seurer/gcc/gcc-test2/libstdc++-v3/libsupc++ -I/home/seurer/gcc/gcc-test2/libstdc++-v3/include/backward -I/home/seurer/gcc/gcc-test2/libstdc++-v3/testsuite/util -O2 -B/home/seurer/gcc/build/gcc-test2/powerpc64-unknown-linux-gnu/./libgomp/..= /libstdc++-v3/src/.libs -L/home/seurer/gcc/build/gcc-test2/powerpc64-unknown-linux-gnu/./libgomp/.l= ibs -L/home/seurer/gcc/build/gcc-test2/powerpc64-unknown-linux-gnu/./libgomp/..= /libstdc++-v3/src/.libs -lstdc++ -lm -o ./cancel-taskgroup-3.exe PASS: libgomp.c++/../libgomp.c-c++-common/cancel-taskgroup-3.c (test for ex= cess errors) Setting LD_LIBRARY_PATH to .:/home/seurer/gcc/build/gcc-test2/powerpc64-unknown-linux-gnu/./libgomp/.l= ibs:/home/seurer/gcc/build/gcc-test2/gcc:/home/seurer/gcc/build/gcc-test2/p= owerpc64-unknown-linux-gnu/./libgomp/../libstdc++-v3/src/.libs:.:/home/seur= er/gcc/build/gcc-test2/powerpc64-unknown-linux-gnu/./libgomp/.libs:/home/se= urer/gcc/build/gcc-test2/gcc:/home/seurer/gcc/build/gcc-test2/powerpc64-unk= nown-linux-gnu/./libgomp/../libstdc++-v3/src/.libs:/home/seurer/gcc/build/g= cc-test2/./gmp/.libs:/home/seurer/gcc/build/gcc-test2/./prev-gmp/.libs:/hom= e/seurer/gcc/build/gcc-test2/./mpfr/src/.libs:/home/seurer/gcc/build/gcc-te= st2/./prev-mpfr/src/.libs:/home/seurer/gcc/build/gcc-test2/./mpc/src/.libs:= /home/seurer/gcc/build/gcc-test2/./prev-mpc/src/.libs:/home/seurer/gcc/buil= d/gcc-test2/./isl/.libs:/home/seurer/gcc/build/gcc-test2/./prev-isl/.libs:/= home/seurer/gcc/install/gcc-7.2.0/lib64 Execution timeout is: 300 spawn [open ...] FAIL: libgomp.c++/../libgomp.c-c++-common/cancel-taskgroup-3.c execution te= st >>From gcc-bugs-return-620913-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 19:54:02 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 92651 invoked by alias); 12 Nov 2018 19:54: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 92551 invoked by uid 48); 12 Nov 2018 19:53:57 -0000 From: "wilco at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/81800] [8 regression] on aarch64 ilp32 lrint should not be inlined as two instructions Date: Mon, 12 Nov 2018 19:54:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: wilco at gcc dot gnu.org X-Bugzilla-Status: REOPENED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: tnfchris at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.0 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: 2018-11/txt/msg01070.txt.bz2 Content-length: 956 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81800 Wilco changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |wilco at gcc dot gnu.org Resolution|FIXED |--- --- Comment #10 from Wilco --- This isn't fixed since GCC now emits for the example (-mabi=3Dilp32 -O2 -fno-math-errno -ftrapping-math -fno-fp-int-builtin-inexact): f: frintx d0, d0 fcvtzs x0, d0 ret So it is now ignoring FE_INVALID. The underlying reason is the builtin expansion of lrint automatically falls back to llrint if lrint optab doesn't exist. The fix is disabling lrint if the floating type size is larger than sizeof(long) so the lrint library function is called instead. >>From gcc-bugs-return-620914-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 20:06:26 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 73383 invoked by alias); 12 Nov 2018 20:06: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 73349 invoked by uid 48); 12 Nov 2018 20:06:21 -0000 From: "jozef.l at mittosystems dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/87996] New: [8/9 Regression] "size of array is negative" error when SIZE_MAX/2 < sizeof(array) <= SIZE_MAX Date: Mon, 12 Nov 2018 20:06:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jozef.l at mittosystems 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: 2018-11/txt/msg01071.txt.bz2 Content-length: 2084 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87996 Bug ID: 87996 Summary: [8/9 Regression] "size of array is negative" error when SIZE_MAX/2 < sizeof(array) <=3D SIZE_MAX Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: jozef.l at mittosystems dot com Target Milestone: --- Created attachment 44992 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D44992&action=3Dedit tester.ii In GCC 7.3, declaring an array of size SIZE_MAX results in an error because= =20 the size of the array is too large. tester.c: #include char array[SIZE_MAX]; gcc tester.c > tester.c:3:6: error: size of array 'array' is too large > char array[SIZE_MAX]; g++ tester.c > tester.c:3:19: error: size of array 'array' is too large > char array[SIZE_MAX]; In GCC 8.1 and current trunk, the error message when compiling C code is the same, but for C++, the size of the array is reported to be negative. gcc tester.c > tester.c:3:6: error: size of array =E2=80=98array=E2=80=99 is too large > 3 | char array[SIZE_MAX]; g++ tester.c > tester.c:3:19: error: size of array =E2=80=98array=E2=80=99 is negative > 3 | char array[SIZE_MAX]; For G++ I tried with -std=3Dc++{98,11,14} and the behaviour was the same. For SIZE_MAX/2, compilation completes succesfully, and the same errors occur for (SIZE_MAX/2+1) According to cppreference (https://en.cppreference.com/w/cpp/language/array) the array size initializer (i.e. the value within []), is either an integral constant expression (until C++14), or a constant expression of type size_t. So in none of these cases should the size of the array be considered to be negative as SIZE_MAX will always fit in a integral constant expression, or size_t, so should never wrap to a negative value. I've attached the pre-processed source applicable for 64-bit size_t. Observed with x86_64-pc-linux-gnu and msp430-elf >>From gcc-bugs-return-620915-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 20:07:42 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 82421 invoked by alias); 12 Nov 2018 20:07:42 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 82383 invoked by uid 48); 12 Nov 2018 20:07:38 -0000 From: "jozef.l at mittosystems dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/87996] [8/9 Regression] "size of array is negative" error when SIZE_MAX/2 < sizeof(array) <= SIZE_MAX Date: Mon, 12 Nov 2018 20:07:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jozef.l at mittosystems dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.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: 2018-11/txt/msg01072.txt.bz2 Content-length: 536 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87996 Jozef Lawrynowicz changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #44992|0 |1 is obsolete| | --- Comment #1 from Jozef Lawrynowicz --- Created attachment 44993 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D44993&action=3Dedit tester.ii >>From gcc-bugs-return-620917-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 20:18:30 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 8052 invoked by alias); 12 Nov 2018 20:18: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 7978 invoked by uid 48); 12 Nov 2018 20:18:26 -0000 From: "gscfq@t-online.de" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/87994] ICE in match_data_constant, at fortran/decl.c:399 Date: Mon, 12 Nov 2018 20:18:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gscfq@t-online.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: 2018-11/txt/msg01074.txt.bz2 Content-length: 400 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87994 --- Comment #1 from G. Steinmetz --- > Should be valid code, ... Whoops, suboptimal. Better examples : $ cat z3.f90 program p real, parameter :: a =3D 1.0 data b /a%kind/ end $ cat z4.f90 program p integer, parameter :: a =3D 1 integer :: b data b /a%kind/ end Changed between 20181028 and 20181104 (ICE). >>From gcc-bugs-return-620916-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 20:18:04 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 7163 invoked by alias); 12 Nov 2018 20:18: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 6998 invoked by uid 48); 12 Nov 2018 20:17:59 -0000 From: "amonakov at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug inline-asm/87984] [7/8/9 Regression] wrong code for local reg var input to asm Date: Mon, 12 Nov 2018 20:18:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: inline-asm X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: amonakov at gcc dot gnu.org X-Bugzilla-Status: REOPENED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01073.txt.bz2 Content-length: 518 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87984 --- Comment #9 from Alexander Monakov --- Actually, no long division needed, broken with a plain move as well: __attribute__((weak)) int f(void) { int o=3D0, i; for (i=3D0; i<3; i++) { register int a asm("eax"); a =3D 1; asm("add %1, %0" : "+r"(o) : "r"(a)); asm("xor %%eax, %%eax" ::: "eax"); } return o; } int main() { if (f() !=3D 3) __builtin_abort(); return 0; } >>From gcc-bugs-return-620918-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 20:19:32 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 10475 invoked by alias); 12 Nov 2018 20:19: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 10405 invoked by uid 48); 12 Nov 2018 20:19:27 -0000 From: "gscfq@t-online.de" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/87993] ICE in gfc_constructor_first, at fortran/constructor.c:234 Date: Mon, 12 Nov 2018 20:19:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gscfq@t-online.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: 2018-11/txt/msg01075.txt.bz2 Content-length: 156 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87993 --- Comment #1 from G. Steinmetz --- Changed between 20181028 and 20181104 (ICE). >>From gcc-bugs-return-620920-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 20:25:30 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 52766 invoked by alias); 12 Nov 2018 20:25: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 52157 invoked by uid 48); 12 Nov 2018 20:25:24 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/87997] [9 Regression] ICE in cp_var_mod_type_p at gcc/cp/cp-objcp-common.c:107 since r265870 Date: Mon, 12 Nov 2018 20:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: lto X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org X-Bugzilla-Target-Milestone: 9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cf_reconfirmed_on cf_known_to_work assigned_to 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: 2018-11/txt/msg01077.txt.bz2 Content-length: 548 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87997 Martin Li=C5=A1ka changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2018-11-12 Known to work| |8.2.0 Assignee|unassigned at gcc dot gnu.org |hubicka at gcc dot = gnu.org Target Milestone|--- |9.0 Known to fail| |9.0 >>From gcc-bugs-return-620919-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 12 20:25:13 2018 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 50740 invoked by alias); 12 Nov 2018 20: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 50337 invoked by uid 48); 12 Nov 2018 20:24:46 -0000 From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/87997] New: [9 Regression] ICE in cp_var_mod_type_p at gcc/cp/cp-objcp-common.c:107 since r265870 Date: Mon, 12 Nov 2018 20:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: lto X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-11/txt/msg01076.txt.bz2 Content-length: 2777 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87997 Bug ID: 87997 Summary: [9 Regression] ICE in cp_var_mod_type_p at gcc/cp/cp-objcp-common.c:107 since r265870 Product: gcc Version: 9.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: lto Assignee: unassigned at gcc dot gnu.org Reporter: marxin at gcc dot gnu.org CC: marxin at gcc dot gnu.org Target Milestone: --- Following is causing ICE: $ cat free.ii template struct a; template