public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: pb@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, kediger@licor.com, nobody@gcc.gnu.org, pb@gcc.gnu.org Subject: Re: target/4860: [ARM; 3.0] sjlj_mark_call_sites thwarted by load-multi Date: Tue, 22 Jan 2002 15:07:00 -0000 [thread overview] Message-ID: <20020122230716.28270.qmail@sources.redhat.com> (raw) Old Synopsis: Internal Compiler Error with ARM g++ cross compiler New Synopsis: [ARM; 3.0] sjlj_mark_call_sites thwarted by load-multi Responsible-Changed-From-To: unassigned->pb Responsible-Changed-By: pb Responsible-Changed-When: Tue Jan 22 15:07:15 2002 Responsible-Changed-Why: . State-Changed-From-To: open->analyzed State-Changed-By: pb State-Changed-When: Tue Jan 22 15:07:15 2002 State-Changed-Why: Still occurs with 3.0 branch. This loop in sjlj_mark_call_sites (about line 2135) is too simple minded: /* Search backward for the first set of a register in this set. */ while (nparm_regs) { before = PREV_INSN (before); /* Given that we've done no other optimizations yet, the arguments should be immediately available. */ if (GET_CODE (before) == CODE_LABEL) abort (); p = single_set (before); if (p && GET_CODE (SET_DEST (p)) == REG && REGNO (SET_DEST (p)) < FIRST_PSEUDO_REGISTER && TEST_HARD_REG_BIT (parm_regs, REGNO (SET_DEST (p)))) { CLEAR_HARD_REG_BIT (parm_regs, REGNO (SET_DEST (p))); nparm_regs--; } } What happens in this case is that several of the SETs for argument registers have been wrapped up in a PARALLEL in order to make them come out as an LDM, which stops single_set from seeing them. This code has already been restructured on the trunk to use note_stores, which avoids the problem. See: Sun Jul 29 23:26:50 CEST 2001 Jan Hubicka <jh@suse.cz> * rtlanal.c (parms_set, find_first_parameter_load): Break out from...; handle multiple sets. * except.c (sjlj_mark_call_sites): .... here. * gcse.c (insert_insn_end_bb): Use find_first_parameter_load. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4860
next reply other threads:[~2002-01-22 23:07 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-22 15:07 pb [this message] 2002-02-11 5:51 pb 2002-02-13 14:28 pb
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=20020122230716.28270.qmail@sources.redhat.com \ --to=pb@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=kediger@licor.com \ --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).