public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/63595] [5.0 Regression] Segmentation faults inside kernel Date: Mon, 03 Nov 2014 19:05:00 -0000 [thread overview] Message-ID: <bug-63595-4-EREMbNTX2y@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63595-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63595 --- Comment #8 from Martin Liška <marxin at gcc dot gnu.org> --- Same problem can be even seen on x86_64-linux-pc: _ZNK13TriangulationILi3EE3endEv: .LFB5569: .cfi_startproc >>>>> subq $24, %rsp .cfi_def_cfa_offset 32 movq %rsp, %rdi call _ZNK13TriangulationILi3EE8end_quadEv addq $24, %rsp .cfi_def_cfa_offset 8 ret .cfi_endproc _ZNK13TriangulationILi3EE8end_quadEv: .LFB2586: .loc 3 2901 0 .cfi_startproc .LVL898: .loc 3 2901 0 movq %rdi, %rax .LBB27759: .LBB27760: .LBB27761: .LBB27762: .loc 14 41 0 movl $-1, (%rdi) movl $-1, 4(%rdi) movq %rsi, 8(%rdi) .LBE27762: .LBE27761: .LBE27760: .LBE27759: .loc 3 2905 0 ret .cfi_endproc Body of the function is created as tail-call trunk by IPA-ICF: Triangulation<dim>::raw_cell_iterator Triangulation<dim>::end() const [with int dim = 3; Triangulation<dim>::raw_cell_iterator = TriaRawIterator<3, CellAccessor<3> >] (const struct Triangulation * const this) { ;; basic block 2, loop depth 0 ;; pred: ENTRY Triangulation<3>::end_quad (this_2(D)); [tail call] return; ;; succ: EXIT } ;; Generating RTL for gimple basic block 2 ;; Triangulation<3>::end_quad (this_2(D)); [tail call] (insn 7 6 8 (parallel [ (set (reg:DI 85) (plus:DI (reg/f:DI 78 virtual-stack-vars) (const_int -16 [0xfffffffffffffff0]))) (clobber (reg:CC 17 flags)) ]) -1 (nil)) (insn 8 7 9 (set (reg:DI 4 si) (reg/f:DI 84 [ this ])) -1 (nil)) (insn 9 8 10 (set (reg:DI 5 di) (reg:DI 85)) -1 (nil)) (call_insn 10 9 0 (call (mem:QI (symbol_ref/i:DI ("_ZNK13TriangulationILi3EE8end_quadEv") [flags 0x1] <function_decl 0x7ff17d629bd0 end_quad>) [0 end_quad S1 A8]) (const_int 0 [0])) -1 (expr_list:REG_CALL_DECL (symbol_ref/i:DI ("_ZNK13TriangulationILi3EE8end_quadEv") [flags 0x1] <function_decl 0x7ff17d629bd0 end_quad>) (expr_list:REG_EH_REGION (const_int 0 [0]) (nil))) (expr_list:DI (use (reg:DI 5 di)) (expr_list:DI (use (reg:DI 4 si)) (nil)))) >From gcc-bugs-return-465661-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 03 19:17:52 2014 Return-Path: <gcc-bugs-return-465661-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 18899 invoked by alias); 3 Nov 2014 19:17:52 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 18874 invoked by uid 48); 3 Nov 2014 19:17:48 -0000 From: "rippey.e at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/62272] Gimplify throws error on method call from inside nested lambdas Date: Mon, 03 Nov 2014 19:17:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 4.9.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: major X-Bugzilla-Who: rippey.e at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: <bug-62272-4-cmKoB1n6Pz@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-62272-4@http.gcc.gnu.org/bugzilla/> References: <bug-62272-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-11/txt/msg00133.txt.bz2 Content-length: 370 https://gcc.gnu.org/bugzilla/show_bug.cgi?idb272 rippey.e at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rippey.e at gmail dot com --- Comment #2 from rippey.e at gmail dot com --- Still broken in 4.9.2.
next prev parent reply other threads:[~2014-11-03 19:05 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-10-19 18:29 [Bug c/63595] New: " sasha.levin at oracle dot com 2014-10-19 18:34 ` [Bug tree-optimization/63595] " pinskia at gcc dot gnu.org 2014-10-19 18:48 ` sasha.levin at oracle dot com 2014-10-19 18:53 ` pinskia at gcc dot gnu.org 2014-10-20 12:53 ` rguenth at gcc dot gnu.org 2014-10-22 1:51 ` pthaugen at gcc dot gnu.org 2014-10-23 17:46 ` [Bug tree-optimization/63595] [5.0 Regression] " pthaugen at gcc dot gnu.org 2014-10-24 2:33 ` mliska at suse dot cz 2014-11-03 19:05 ` marxin at gcc dot gnu.org [this message] 2014-11-04 10:18 ` marxin at gcc dot gnu.org 2014-11-05 16:50 ` marxin at gcc dot gnu.org 2014-11-07 12:33 ` marxin at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-63595-4-EREMbNTX2y@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).