From: Oleg Endo <oleg.endo@t-online.de>
To: John Cotton Ericson <Ericson2314@yahoo.com>
Cc: Andrew Haley <aph@redhat.com>, gcc-help@gcc.gnu.org
Subject: Re: GCC vs MSVC compiler issues in a port
Date: Fri, 28 Dec 2012 23:46:00 -0000 [thread overview]
Message-ID: <1356738364.2359.6.camel@yam-132-YW-E178-FTW> (raw)
In-Reply-To: <50D6991B.1070904@yahoo.com>
On Sun, 2012-12-23 at 00:39 -0500, John Cotton Ericson wrote:
> I agree, I tried to make my inline assembly as match the original as
> much is possible. But you just can't rule it out while it's still there.
Well, as a first step, I'd replace all inline asm stuff with C/C++
implementations in the original version using MSVC. Performance might
become worse than the original, or it might not. Either way, I'd leave
those optimizations for later. Moreover, it would give you a CPU
independent version of the code, which is often a good thing :)
> For testing would you recommend something like
> http://check.sourceforge.net/ ?
A test_main with a bunch of assert checks should suffice as a start.
Cheers,
Oleg
next prev parent reply other threads:[~2012-12-28 23:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50D57597.7050304@yahoo.com>
2012-12-22 9:07 ` John Cotton Ericson
2012-12-22 12:11 ` Oleg Endo
2012-12-23 5:39 ` John Cotton Ericson
2012-12-27 13:10 ` David Brown
2012-12-28 23:46 ` Oleg Endo [this message]
2013-01-18 22:31 ` John Cotton Ericson
2012-12-22 16:31 ` Andrew Haley
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=1356738364.2359.6.camel@yam-132-YW-E178-FTW \
--to=oleg.endo@t-online.de \
--cc=Ericson2314@yahoo.com \
--cc=aph@redhat.com \
--cc=gcc-help@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).