public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Diego Novillo <dnovillo@redhat.com> To: law@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/10862: [tree-ssa] Segfault for (essentially) empty function Date: Mon, 19 May 2003 15:36:00 -0000 [thread overview] Message-ID: <20030519153600.3755.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/10862; it has been noted by GNATS. From: Diego Novillo <dnovillo@redhat.com> To: bangerth@dealii.org, bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, law@gcc.gnu.org, nobody@gcc.gnu.org, "gcc-gnats@gcc.gnu.org" <gcc-gnats@gcc.gnu.org> Cc: Subject: Re: optimization/10862: [tree-ssa] Segfault for (essentially) empty function Date: 19 May 2003 11:27:21 -0400 On Mon, 2003-05-19 at 10:51, bangerth@dealii.org wrote: > Synopsis: [tree-ssa] Segfault for (essentially) empty function > > Responsible-Changed-From-To: unassigned->law > Responsible-Changed-By: bangerth > Responsible-Changed-When: Mon May 19 14:51:18 2003 > Responsible-Changed-Why: > Jeff, you had been doing the tree-ssa C++ stuff, right? Or > is there someone else whom I could bother? > It's not actually a C++ problem. It was a bug in DCE when removing a conditional that had no basic blocks after it. > Besides, apart from this one and 10863 (which triggers > _really_ frequent on my code), the tree-ssa branch seems > to be in pretty good shape -- thanks! > I'm glad to hear that. Thanks for testing! Diego.
next reply other threads:[~2003-05-19 15:36 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-19 15:36 Diego Novillo [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-19 22:07 bangerth 2003-05-19 22:06 Wolfgang Bangerth 2003-05-19 18:16 law 2003-05-19 15:16 Diego Novillo 2003-05-19 14:51 bangerth 2003-05-19 14:46 bangerth
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=20030519153600.3755.qmail@sources.redhat.com \ --to=dnovillo@redhat.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=law@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).