From: "Naveen Sharma, Noida" <naveens@noida.hcltech.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: gcc@gcc.gnu.org, Sanjiv Gupta <skg@cradle.com>
Subject: Re: Register Spilling
Date: Thu, 11 Dec 2003 13:53:00 -0000 [thread overview]
Message-ID: <1B3885BC15C7024C845AAC78314766C50187E467@exch-01.noida.hcltech.com> (raw)
> On Thu, 11 Dec 2003, Naveen Sharma, Noida wrote:
>> This was the last post.
>> http://gcc.gnu.org/ml/gcc-patches/2003-01/msg02567.html
>>
>> Do let me know if you are interesred to use this.
>
> (FWIW, I am.)
>
>> This has
>> not been checked in the mainline. For patches like this
>> to go into mainline, they should be tested for atleast 5 gcc
>> targets. I couldn't do that.
>
>Yes you can: <URL:http://gcc.gnu.org/simtest-howto.html> tells
>you how.
Thanks, I knew this but for an optimization patch, we
need to prove that it actually improves (or doesn't degrade)
code for (N >= 5) targets. This IMHO requires significant effort.
But since there is interest on this, I can do simulator
test with latest version of the patch, but not in a position to
fix problems except sh-elf.
> Certainly many of the target listed fail to build
This would probably have to be tested on tree-ssa branch now, right?
Let me check what additional problems arise.
Best Regards,
Naveen Sharma.
> should be able to find five even without including your host
> computer.
> Last I checked, arm-elf, m32r-elf, mips-elf,
> mn10300-elf, v850-elf and sh-elf worked (perhaps others do, but
> I don't test all the listed ones). Oh, you can test using MMIX
> too; put Knuth's simulator named "mmix", linked from
> <URL:http://www-cs-faculty.stanford.edu/~knuth/mmix-news.html>
> somewhere in your PATH, use --target_board=mmixware-sim.
>
> brgds, H-P
next reply other threads:[~2003-12-11 13:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 13:53 Naveen Sharma, Noida [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-11 11:11 Naveen Sharma, Noida
2003-12-11 13:22 ` Hans-Peter Nilsson
[not found] <jsm@polyomino.org.uk>
2003-12-10 14:08 ` (printf) ("hello world\n"); Joseph S. Myers
2003-12-10 14:19 ` Register Spilling Umar Janjua
2003-12-11 7:59 ` Jim Wilson
2003-12-11 9:01 ` Sanjiv Gupta
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=1B3885BC15C7024C845AAC78314766C50187E467@exch-01.noida.hcltech.com \
--to=naveens@noida.hcltech.com \
--cc=gcc@gcc.gnu.org \
--cc=hp@bitrange.com \
--cc=skg@cradle.com \
/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).