public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: jeroen dobbelaere <jeroen.dobbelaere@acunia.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/5828: gcc-3.0.4 on arm : floating point registers incorrectly reloaded Date: Tue, 05 Mar 2002 02:56:00 -0000 [thread overview] Message-ID: <20020305105605.14573.qmail@sources.redhat.com> (raw) The following reply was made to PR target/5828; it has been noted by GNATS. From: jeroen dobbelaere <jeroen.dobbelaere@acunia.com> To: jeroen dobbelaere <jeroen.dobbelaere@acunia.com> Cc: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-patches@gcc.gnu.org Subject: Re: target/5828: gcc-3.0.4 on arm : floating point registers incorrectly reloaded Date: Tue, 05 Mar 2002 11:51:06 +0100 This is a multi-part message in MIME format. --------------040707040700090206020008 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5828 This patch resolves the problem. It has been bootstrapped and introduced no new regressions. Greetings -- Jeroen Dobbelaere Embedded Software Engineer ACUNIA Embedded Solutions http://www.acunia.com --------------040707040700090206020008 Content-Type: text/plain; name="gcc-3.0.4-float-reload-jdo-1.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="gcc-3.0.4-float-reload-jdo-1.patch" diff -rC5 gcc-3.0.4/gcc/ChangeLog gcc-3.0.4-jdo1/gcc/ChangeLog *** gcc-3.0.4/gcc/ChangeLog Mon Mar 4 17:40:43 2002 --- gcc-3.0.4-jdo1/gcc/ChangeLog Mon Mar 4 17:39:35 2002 *************** *** 1,5 **** --- 1,10 ---- + 2002-03-04 Jeroen Dobbelaere <jeroen.dobbelaere@acunia.com> + + * config/arm/arm.c (arm_output_epilogue): bug 5828 : offset + must start at 0 in stead of 12. + 2002-02-20 Release Manager * GCC 3.0.4 Released. 2002-02-20 Release Manager Only in gcc-3.0.4-jdo1/gcc: ChangeLog~ diff -rC5 gcc-3.0.4/gcc/config/arm/arm.c gcc-3.0.4-jdo1/gcc/config/arm/arm.c *** gcc-3.0.4/gcc/config/arm/arm.c Mon Mar 4 17:40:56 2002 --- gcc-3.0.4-jdo1/gcc/config/arm/arm.c Mon Mar 4 17:38:15 2002 *************** *** 7315,7326 **** int really_return; { int reg; unsigned long saved_regs_mask; unsigned long func_type; ! /* If we need this, then it will always be at least this much. */ ! int floats_offset = 12; rtx operands[3]; int frame_size = get_frame_size (); FILE * f = asm_out_file; rtx eh_ofs = cfun->machine->eh_epilogue_sp_ofs; --- 7315,7326 ---- int really_return; { int reg; unsigned long saved_regs_mask; unsigned long func_type; ! /* Offset is computed as needed, start from -4. (fp points to stack entry-4) */ ! int floats_offset = -4; rtx operands[3]; int frame_size = get_frame_size (); FILE * f = asm_out_file; rtx eh_ofs = cfun->machine->eh_epilogue_sp_ofs; Only in gcc-3.0.4-jdo1/gcc/config/arm: arm.c~ --------------040707040700090206020008--
next reply other threads:[~2002-03-05 10:56 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-05 2:56 jeroen dobbelaere [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-03-14 7:54 rearnsha 2002-03-14 7:16 Richard Earnshaw 2002-03-06 3:46 jeroen dobbelaere 2002-03-06 2:36 Richard Earnshaw 2002-03-05 2:56 jeroen dobbelaere 2002-03-04 7:06 jeroen.dobbelaere
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=20020305105605.14573.qmail@sources.redhat.com \ --to=jeroen.dobbelaere@acunia.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).