All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: Eric DeVolder <edevolder@razamicroelectronics.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Differing results from cross and native compilers
Date: Tue, 19 Sep 2006 18:16:24 +0100	[thread overview]
Message-ID: <20060919171624.GA24864@networkno.de> (raw)
In-Reply-To: <2E96546B3C2C8B4CA739323C6058204A0163548C@hq-ex-mb01.razamicroelectronics.com>

Eric DeVolder wrote:
> Yes, it appears to me that the compiler (cc1) and assembler (as)
> invocations are the same. I've included the "-v" output of each
> below for reference. Furthermore, the -save-temps output .i files
> are effectively the same (differences due to cross vs. native paths,
> but that is it). Nonetheless, the output assembly source still
> contains differences!
>  
> I'm curious if anybody examined the output of a cross and native
> toolchain of the same (recent) version?

I get the same (properly optimised) result from both compilers:

  gcc (GCC) 4.1.2 20060901 (prerelease) (Debian 4.1.1-13)
  mips-linux-gnu-gcc (GCC) 4.1.2 20060901 (prerelease) (Debian 4.1.1-13)


I haven't tried a 3.4 crosscompiler, but the native one also behaves
as expected:

  gcc-3.4 (GCC) 3.4.6 (Debian 3.4.6-4)


Thiemo

  reply	other threads:[~2006-09-19 17:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-19 16:57 Differing results from cross and native compilers Eric DeVolder
2006-09-19 16:57 ` Eric DeVolder
2006-09-19 17:16 ` Thiemo Seufer [this message]
2006-09-19 17:18 ` David Daney
2006-09-19 23:22 ` Jim Wilson
  -- strict thread matches above, loose matches on Subject: below --
2006-09-21 14:53 Eric DeVolder
2006-09-21 14:53 ` Eric DeVolder
2006-09-21 14:26 Eric DeVolder
2006-09-21 14:26 ` Eric DeVolder
2006-09-19 17:56 Eric DeVolder
2006-09-19 17:56 ` Eric DeVolder
2006-09-19 21:08 ` Thiemo Seufer
2006-09-19 15:39 Eric DeVolder
2006-09-19 15:39 ` Eric DeVolder
2006-09-19 16:05 ` Thiemo Seufer

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=20060919171624.GA24864@networkno.de \
    --to=ths@networkno.de \
    --cc=edevolder@razamicroelectronics.com \
    --cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.