From: n8tm@aol.comnojunk (Tim Prince)
To: help-gcc@gnu.org
Subject: Re: gcc-2.95.2
Date: Tue, 30 Nov 1999 23:28:00 -0000 [thread overview]
Message-ID: <19991108220845.07026.00003706@ng-cg1.aol.com> (raw)
Message-ID: <19991130232800.-q5QG2tai28S80XLxm1l_uTBIpywXbFdJ_ZERX62uqw@z> (raw)
In-Reply-To: <3826D6F0.82D43CE4@bcpl.net>
>when i install prebuilt binaries, is it less
>efficient than binaries built on my own system
I suppose this question could be interpreted various ways, and I'm not fully
competent to answer, as I haven't tried both ways. Maybe I'll get Mumit's
version and compare output files. I expect the results would be the same
except for possible alignment differences; I've put some emphasis on getting
the .p2align scheme working when building natively, even though it is not fully
effective because of cygwin not providing 128-bit stack alignment. You would
see this by comparing .s files, for example; the alignment directives may
differ. Also, you probably wouldn't be using exactly the same binutils, if
Mumit is recommending you install his binaries for both binutils and the
compilers.
Tim Prince
tprince@computer.org
next prev parent reply other threads:[~1999-11-30 23:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-06 13:08 gcc-2.95.2 Inferno
1999-11-06 14:50 ` gcc-2.95.2 Tim Prince
1999-11-06 17:09 ` gcc-2.95.2 Inferno
1999-11-07 22:52 ` gcc-2.95.2 Mumit Khan
1999-11-08 5:55 ` gcc-2.95.2 Inferno
1999-11-30 23:28 ` gcc-2.95.2 Inferno
1999-11-08 5:58 ` gcc-2.95.2 Inferno
1999-11-08 19:09 ` Tim Prince [this message]
1999-11-30 23:28 ` gcc-2.95.2 Tim Prince
1999-11-30 23:28 ` gcc-2.95.2 Inferno
1999-11-30 23:28 ` gcc-2.95.2 Mumit Khan
1999-11-30 23:28 ` gcc-2.95.2 Inferno
1999-11-30 23:28 ` gcc-2.95.2 Tim Prince
1999-11-30 23:28 ` gcc-2.95.2 Inferno
2001-02-21 22:29 gcc-2.95.2 Agung Yogaswara
2001-02-21 23:12 ` gcc-2.95.2 Alexandre Oliva
2001-02-22 17:50 ` gcc-2.95.2 Agung Yogaswara
2001-02-22 18:08 ` gcc-2.95.2 Agung Yogaswara
2001-02-21 23:18 ` gcc-2.95.2 Jerry Miller
2001-02-22 17:50 ` gcc-2.95.2 Agung Yogaswara
2001-02-22 18:00 ` gcc-2.95.2 Jerry Miller
2001-02-22 18:08 ` gcc-2.95.2 Agung Yogaswara
2001-02-22 10:46 ` gcc-2.95.2 sherry
2001-02-22 10:50 ` gcc-2.95.2 sherry
2001-03-16 7:29 gcc-2.95.2 Jumblat, Ghassan
2001-03-16 8:13 gcc-2.95.2 David Korn
2001-10-29 20:09 gcc-2.95.2 sachin lamsoge
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=19991108220845.07026.00003706@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).