public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marcus@mc.pp.se" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/6526] [SH4] sdivsi3_i4 can clobber xd0/xd2
Date: Mon, 02 Jun 2003 12:25:00 -0000 [thread overview]
Message-ID: <20030602122558.792.qmail@sources.redhat.com> (raw)
In-Reply-To: <20020430191600.6526.marcus@mc.pp.se>
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=6526
------- Additional Comments From marcus@mc.pp.se 2003-06-02 12:25 -------
Subject: Re: [SH4] sdivsi3_i4 can clobber xd0/xd2
"joern.rennecke@superh.com" <gcc-bugzilla@gcc.gnu.org> writes:
> If you want to change fpscr so that the change is effecitve and preserved
> in and across function calls, you should use __set_fpscr.
> The new value for fpscr is to be passed in r4, and it is put in fpscr,
> and with appropriate modifications to the PR and SZ bit into the two
> locations of __fpscr_values.
Sorry, but this isn't really helpful. First, the current libgcc
functions do _not_ use __fpscr_values, so using __set_fpscr won't help
anyway (as you can see in the test case, which _does_ use __set_fpscr
but still fails). Second, I need to use frchg for preformance reasons.
// Marcus
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2003-06-02 12:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020430191600.6526.marcus@mc.pp.se>
2003-06-02 11:40 ` joern.rennecke@superh.com
2003-06-02 12:25 ` marcus@mc.pp.se [this message]
2003-06-03 15:55 ` joern.rennecke@superh.com
2003-06-03 17:14 ` marcus@mc.pp.se
2003-06-03 18:40 ` joern.rennecke@superh.com
2003-06-03 19:19 ` marcus@mc.pp.se
2003-06-16 18:18 ` dhazeghi@yahoo.com
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=20030602122558.792.qmail@sources.redhat.com \
--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: link
Be 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).