All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Daney <ddaney@avtrex.com>
To: Eric DeVolder <edevolder@razamicroelectronics.com>
Cc: Thiemo Seufer <ths@networkno.de>, linux-mips@linux-mips.org
Subject: Re: Differing results from cross and native compilers
Date: Tue, 19 Sep 2006 10:18:46 -0700	[thread overview]
Message-ID: <45102676.6040800@avtrex.com> (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?
>  

Some of the code generation options of the compiler are set to default 
values which are controlled by options passed to the compiler's 
configure program.

Unless identical configure options are used in the native and cross 
builds, you might different default code generation options.

David Daney

  parent reply	other threads:[~2006-09-19 17:18 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
2006-09-19 17:18 ` David Daney [this message]
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=45102676.6040800@avtrex.com \
    --to=ddaney@avtrex.com \
    --cc=edevolder@razamicroelectronics.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ths@networkno.de \
    /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.