public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/9929: [3.3/3.4 regression] Can't find spill register Date: Mon, 24 Mar 2003 22:46:00 -0000 [thread overview] Message-ID: <20030324220600.15888.qmail@sources.redhat.com> (raw) The following reply was made to PR target/9929; it has been noted by GNATS. From: Janis Johnson <janis187@us.ibm.com> To: Steven Bosscher <s.bosscher@student.tudelft.nl> Cc: gabor@mac.com, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-prs@gcc.gnu.org, janis187@us.ibm.com, jh@suse.cz Subject: Re: target/9929: [3.3/3.4 regression] Can't find spill register Date: Mon, 24 Mar 2003 14:04:19 -0800 On Mon, Mar 24, 2003 at 09:00:40PM +0100, Steven Bosscher wrote: > > Janis, can you hunt this one? The regression showed up with this patch: Sat Mar 30 14:08:55 CET 2002 Jan Hubicka <jh@suse.cz> * local-alloc.c (local_alloc): Avoid call of update_equiv_regs when not optimizing. * toplev.c (rest_of_compilation): Cann mark_constant_function only when optimizing. * flow.c (calculate_global_regs_live): Ensure that all AUX fields are NULL. * cfgcleanup.c (bb_flags): Add BB_NONTHREADABLE_BLOCK. (thread_jump): Set BB_NONTHREADABLE_BLOCK, check it. (try_optimize_cfg): clear all AUX fields. * i386.c (aligned_operand): Be prepared for SUBREGed registers. (ix86_decompose_address): Use REG_P instead of GET_CODE (...) == REG. (ix86_address_cost): Be prepared for SUBREGed registers. (legitimate_address_p): Accept SUBREGed registers. The hunt used Wolfgang's reduced test case with "-O -fPIC" on i686-pc-linux-gnu.
next reply other threads:[~2003-03-24 22:06 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-24 22:46 Janis Johnson [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-24 23:46 Jan Hubicka 2003-03-24 20:16 Steven Bosscher 2003-03-04 15:22 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=20030324220600.15888.qmail@sources.redhat.com \ --to=janis187@us.ibm.com \ --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).