public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Anders Blomdell <anders.blomdell@control.lth.se> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/6025: linux m68k-elf-gcc cross compiler segfault Date: Fri, 22 Mar 2002 04:46:00 -0000 [thread overview] Message-ID: <20020322124605.15612.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/6025; it has been noted by GNATS. From: Anders Blomdell <anders.blomdell@control.lth.se> To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, anders.blomdell@control.lth.se, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: optimization/6025: linux m68k-elf-gcc cross compiler segfault Date: Fri, 22 Mar 2002 13:39:49 +0100 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6025 OK, I have looked a little furter into this. The problem seems to be in bb-reorder.c:415: next = (taken ? e_taken : e_fall)->dest; the segfault occurs when we get here with: taken = 0, e_taken = 842a0b0, e_fall = 0 (since (0 ? 842a0b0 : 0)->dest == (0)->dest, which is clearly illegal). Now, how do I do to find out why there is a block without a valid fall-through path (mapping *.ce2 dump to basic block layout is beyond my capacity). -- ------------------------------------------------------------------------------ Anders Blomdell Department of Automatic Control Email: anders.blomdell@control.lth.se Lund Institute of Technology Phone: +46 46 222 4625 Box 118, S-221 00 Lund, Sweden Fax: +46 46 138118
next reply other threads:[~2002-03-22 12:46 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-22 4:46 Anders Blomdell [this message] 2002-03-22 7:46 Anders Blomdell 2002-03-27 1:54 rth 2002-04-23 0:47 rth
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=20020322124605.15612.qmail@sources.redhat.com \ --to=anders.blomdell@control.lth.se \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).