public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Segher Boessenkool <segher@koffie.nl> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/9564: compiling sdiff causes ICE on powerpc Date: Wed, 05 Feb 2003 00:16:00 -0000 [thread overview] Message-ID: <20030205001600.21952.qmail@sources.redhat.com> (raw) The following reply was made to PR c/9564; it has been noted by GNATS. From: Segher Boessenkool <segher@koffie.nl> To: nall@gentoo.org Cc: gcc-gnats@gcc.gnu.org, gcc-patches@gcc.gnu.org Subject: Re: c/9564: compiling sdiff causes ICE on powerpc Date: Wed, 05 Feb 2003 00:10:09 +0100 Hi, This patch fixes it; if okay, please install on 3.3 and mainline (and 3.2, too, if that branch is open for this kind of thing; I believe it's not, at the moment :) ). Does something like this need a testcase? If so, in what directory? gcc.dg? A simplified testcase is attached, but I'll write a real testsuite thingy if wanted. Segher /* compile with -maltivec -mabi=altivec -g */ extern int vfork(void); void boom(void) { char buf[65536]; vfork(); } 2003-02-04 Segher Boessenkool <segher@koffie.nl> * config/rs6000/rs6000.c (altivec_frame_fixup): Remove. (rs6000_emit_prologue): Use rs6000_frame_related instead. *** config/rs6000/rs6000.c~ Tue Feb 4 09:23:02 2003 --- config/rs6000/rs6000.c Tue Feb 4 10:51:42 2003 *************** static int first_altivec_reg_to_save PAR *** 262,268 **** static unsigned int compute_vrsave_mask PARAMS ((void)); static void is_altivec_return_reg PARAMS ((rtx, void *)); static rtx generate_set_vrsave PARAMS ((rtx, rs6000_stack_t *, int)); - static void altivec_frame_fixup PARAMS ((rtx, rtx, HOST_WIDE_INT)); static int easy_vector_constant PARAMS ((rtx)); \f /* Default register names. */ --- 262,267 ---- *************** rs6000_emit_allocate_stack (size, copy_r *** 9976,10007 **** REG_NOTES (insn)); } - /* Add a RTX_FRAME_RELATED note so that dwarf2out_frame_debug_expr - knows that: - - (mem (plus (blah) (regXX))) - - is really: - - (mem (plus (blah) (const VALUE_OF_REGXX))). */ - - static void - altivec_frame_fixup (insn, reg, val) - rtx insn, reg; - HOST_WIDE_INT val; - { - rtx real; - - real = copy_rtx (PATTERN (insn)); - - real = replace_rtx (real, reg, GEN_INT (val)); - - RTX_FRAME_RELATED_P (insn) = 1; - REG_NOTES (insn) = gen_rtx_EXPR_LIST (REG_FRAME_RELATED_EXPR, - real, - REG_NOTES (insn)); - } - /* Add to 'insn' a note which is PATTERN (INSN) but with REG replaced with (plus:P (reg 1) VAL), and with REG2 replaced with RREG if REG2 is not NULL. It would be nice if dwarf2out_frame_debug_expr could --- 9975,9980 ---- *************** rs6000_emit_prologue () *** 10299,10305 **** insn = emit_move_insn (mem, savereg); ! altivec_frame_fixup (insn, areg, offset); } } --- 10272,10279 ---- insn = emit_move_insn (mem, savereg); ! rs6000_frame_related (insn, frame_ptr_rtx, info->total_size, ! areg, GEN_INT (offset)); } }
next reply other threads:[~2003-02-05 0:16 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-05 0:16 Segher Boessenkool [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-20 19:54 dje 2003-02-20 8:51 ebotcazou 2003-02-04 4:06 nall
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=20030205001600.21952.qmail@sources.redhat.com \ --to=segher@koffie.nl \ --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).