From: n8tm@aol.comnojunk (Tim Prince)
To: help-gcc@gnu.org
Subject: Re: gcc on different platforms
Date: Sat, 11 Dec 1999 11:10:00 -0000 [thread overview]
Message-ID: <19991211140919.28322.00000148@ng-cg1.aol.com> (raw)
In-Reply-To: <3850F092.3F08B0EF@icn.siemens.de>
>If the version of gcc is the same on both host platforms, does it
>produce the same output (i.e. object files) on different host platforms
>if you always use the same source and header files
>If not, where and what are the differences ??
>
>Thanks in advance,
>
The code block alignments depend on the assembler, and how the compiler is
configured to it. For example, i686 code may be using .p2align 4,,7 in one
configuration, and unconditional 128-bit alignments in another.
Tim Prince
tprince@computer.org
WARNING: multiple messages have this Message-ID
From: n8tm@aol.comnojunk (Tim Prince)
To: help-gcc@gnu.org
Subject: Re: gcc on different platforms
Date: Fri, 31 Dec 1999 22:24:00 -0000 [thread overview]
Message-ID: <19991211140919.28322.00000148@ng-cg1.aol.com> (raw)
Message-ID: <19991231222400.e1CKTRtwPMX3x3mM6IekEsg6sQnavfr5E4YcmPe2jxo@z> (raw)
In-Reply-To: <3850F092.3F08B0EF@icn.siemens.de>
>If the version of gcc is the same on both host platforms, does it
>produce the same output (i.e. object files) on different host platforms
>if you always use the same source and header files
>If not, where and what are the differences ??
>
>Thanks in advance,
>
The code block alignments depend on the assembler, and how the compiler is
configured to it. For example, i686 code may be using .p2align 4,,7 in one
configuration, and unconditional 128-bit alignments in another.
Tim Prince
tprince@computer.org
next prev parent reply other threads:[~1999-12-11 11:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-10 21:48 Daniel Schnell
1999-12-11 11:10 ` Tim Prince [this message]
1999-12-31 22:24 ` Tim Prince
1999-12-11 12:50 ` libstdc++.so Dave Topham
1999-12-31 22:24 ` libstdc++.so Dave Topham
1999-12-11 12:50 ` libstdc++.so Dave Topham
1999-12-31 22:24 ` libstdc++.so Dave Topham
1999-12-11 12:50 ` libstdc++.so Dave Topham
1999-12-31 22:24 ` libstdc++.so Dave Topham
1999-12-31 22:24 ` gcc on different platforms Daniel Schnell
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=19991211140919.28322.00000148@ng-cg1.aol.com \
--to=n8tm@aol.comnojunk \
--cc=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).