From: Joe Buck <jbuck@Synopsys.COM>
To: law@cygnus.com
Cc: zack@rabi.columbia.edu, pfeifer@dbai.tuwien.ac.at, egcs@egcs.cygnus.com
Subject: Re: egcs and Linux kernels
Date: Wed, 10 Mar 1999 11:33:00 -0000 [thread overview]
Message-ID: <199903101931.LAA02190@atrus.synopsys.com> (raw)
In-Reply-To: < 29373.921092478@hurl.cygnus.com >; from "Jeffrey A Law" at Mar 10, 99 12:01 pm
> > - gcc 2.8.1 and egcs (all released versions) may silently generate bad
> > code for the incorrect asm constructs in old kernels
> And "gcc-2.7.2". There's nothing magical about gcc-2.7.2 that prevents it
> losing due to the incorrect asms.
Except that it has been thoroughly tested, and it so happens that at
least if you use the same options the kernel developers used, you don't
get bad code with gcc-2.7.2.
WARNING: multiple messages have this Message-ID
From: Joe Buck <jbuck@Synopsys.COM>
To: law@cygnus.com
Cc: zack@rabi.columbia.edu, pfeifer@dbai.tuwien.ac.at, egcs@egcs.cygnus.com
Subject: Re: egcs and Linux kernels
Date: Wed, 31 Mar 1999 23:46:00 -0000 [thread overview]
Message-ID: <199903101931.LAA02190@atrus.synopsys.com> (raw)
Message-ID: <19990331234600.t4NoHSepBybUD52Ku0cWHBIY2AKjRRSvOxiLEupzFk8@z> (raw)
In-Reply-To: <29373.921092478@hurl.cygnus.com>
> > - gcc 2.8.1 and egcs (all released versions) may silently generate bad
> > code for the incorrect asm constructs in old kernels
> And "gcc-2.7.2". There's nothing magical about gcc-2.7.2 that prevents it
> losing due to the incorrect asms.
Except that it has been thoroughly tested, and it so happens that at
least if you use the same options the kernel developers used, you don't
get bad code with gcc-2.7.2.
next prev parent reply other threads:[~1999-03-10 11:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-10 7:13 Gerald Pfeifer
[not found] ` < Pine.BSF.4.10.9903101606330.44575-100000@alkaid.dbai.tuwien.ac.at >
1999-03-10 7:27 ` Zack Weinberg
[not found] ` < 199903101527.KAA15375@blastula.phys.columbia.edu >
1999-03-10 11:02 ` Jeffrey A Law
[not found] ` < 29373.921092478@hurl.cygnus.com >
1999-03-10 11:05 ` Zack Weinberg
1999-03-31 23:46 ` Zack Weinberg
1999-03-10 11:33 ` Joe Buck [this message]
[not found] ` < 199903101931.LAA02190@atrus.synopsys.com >
1999-03-10 11:35 ` Jeffrey A Law
[not found] ` < 29536.921094521@hurl.cygnus.com >
1999-03-10 11:46 ` Joe Buck
1999-03-31 23:46 ` Joe Buck
1999-03-31 23:46 ` Jeffrey A Law
1999-03-31 23:46 ` Joe Buck
1999-03-31 23:46 ` Jeffrey A Law
1999-03-10 12:27 ` Gerald Pfeifer
1999-03-31 23:46 ` Gerald Pfeifer
1999-03-31 23:46 ` Zack Weinberg
1999-03-31 23:46 ` Gerald Pfeifer
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=199903101931.LAA02190@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=egcs@egcs.cygnus.com \
--cc=law@cygnus.com \
--cc=pfeifer@dbai.tuwien.ac.at \
--cc=zack@rabi.columbia.edu \
/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).