public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/19528] [4.0 regression] missing ra.h Date: Wed, 19 Jan 2005 12:22:00 -0000 [thread overview] Message-ID: <20050119122200.17028.qmail@sourceware.org> (raw) In-Reply-To: <20050119095203.19528.corsepiu@gcc.gnu.org> ------- Additional Comments From steven at gcc dot gnu dot org 2005-01-19 12:21 ------- I am not even going to try and look surprised, the SH port is a major abuser of the middle-end. But of course, hard_regs_intersect_p should have been in hard-reg-set.h from the start, *sigh*, mess-meets-mess. Try this: Index: hard-reg-set.h =================================================================== RCS file: /cvs/gcc/gcc/gcc/hard-reg-set.h,v retrieving revision 1.25 diff -u -3 -p -r1.25 hard-reg-set.h --- hard-reg-set.h 15 Jan 2005 16:06:14 -0000 1.25 +++ hard-reg-set.h 19 Jan 2005 12:21:01 -0000 @@ -499,4 +499,19 @@ extern const char * reg_class_names[]; #define REG_CANNOT_CHANGE_MODE_P(REGN, FROM, TO) \ CANNOT_CHANGE_MODE_CLASS (FROM, TO, REGNO_REG_CLASS (REGN)) +/* Determine if two hard register sets intersect. + Return 1 if they do. */ + +static inline bool +hard_regs_intersect_p (HARD_REG_SET *a, HARD_REG_SET *b) +{ + HARD_REG_SET c; + COPY_HARD_REG_SET (c, *a); + AND_HARD_REG_SET (c, *b); + GO_IF_HARD_REG_SUBSET (c, reg_class_contents[(int) NO_REGS], lose); + return 1; +lose: + return 0; +} + #endif /* ! GCC_HARD_REG_SET_H */ -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19528
next prev parent reply other threads:[~2005-01-19 12:22 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-01-19 9:52 [Bug target/19528] New: " corsepiu at gcc dot gnu dot org 2005-01-19 12:22 ` steven at gcc dot gnu dot org [this message] 2005-01-19 12:26 ` [Bug target/19528] " steven at gcc dot gnu dot org 2005-01-19 12:55 ` paolo dot bonzini at lu dot unisi dot ch 2005-01-19 13:27 ` bonzini at gcc dot gnu dot org 2005-01-19 13:47 ` bonzini at gcc dot gnu dot org 2005-01-19 13:48 ` pinskia at gcc dot gnu dot org 2005-01-19 14:03 ` pinskia at gcc dot gnu dot org 2005-01-19 16:35 ` corsepiu at gcc dot gnu dot org 2005-01-19 19:00 ` steven at gcc dot gnu dot org 2005-01-21 17:34 ` mmitchel at gcc dot gnu dot org 2005-01-22 12:20 ` steven at gcc dot gnu dot org 2005-01-22 12:57 ` joel at gcc dot gnu dot org 2005-01-22 19:43 ` mark at codesourcery dot com 2005-01-24 16:22 ` pinskia at gcc dot gnu dot org 2005-04-20 2:03 ` pinskia at gcc dot gnu dot 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=20050119122200.17028.qmail@sourceware.org \ --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).