From: Joe Buck <jbuck@synopsys.com>
To: Hunter Peress <hu.peress@mail.mcgill.ca>
Cc: gcc@gcc.gnu.org
Subject: Re: when did support for i686 begin
Date: Thu, 02 Jan 2003 22:41:00 -0000 [thread overview]
Message-ID: <20030102144115.A32555@synopsys.com> (raw)
In-Reply-To: <1041537682.9765.22.camel@HillCountryPeress>; from hu.peress@mail.mcgill.ca on Thu, Jan 02, 2003 at 02:01:21PM -0600
On Thu, Jan 02, 2003 at 02:01:21PM -0600, Hunter Peress wrote:
> I dont mean...when was gcc compilable on i686. I mean, when did it start
> having a flag for it...
>
> eg:
> i386 Options
> -m486 -mno-486 -msoft-float -mno-fp-ret-in-387
>
> But for i686.
Hard to determine, since it predates the use of CVS.
> from word of mouth (eg irc probing), it seems like it only began in 3.2,
> i dont believe this. And after searching gcc's site on gnu.org for a
> _while_, its too complex.
*Much* earlier than that, e.g. pre-1996.
That's not to say that the i686 code generated by circa-1996 gcc's was
any good ...
prev parent reply other threads:[~2003-01-02 22:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 19:50 Hunter Peress
2003-01-02 22:41 ` Joe Buck [this message]
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=20030102144115.A32555@synopsys.com \
--to=jbuck@synopsys.com \
--cc=gcc@gcc.gnu.org \
--cc=hu.peress@mail.mcgill.ca \
/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).