From: Jeffrey A Law <law@hurl.cygnus.com>
To: Joe Buck <jbuck@Synopsys.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:35:00 -0000 [thread overview]
Message-ID: <29536.921094521@hurl.cygnus.com> (raw)
In-Reply-To: Your message of Wed, 10 Mar 1999 11:31:16 MST. < 199903101931.LAA02190@atrus.synopsys.com >
In message < 199903101931.LAA02190@atrus.synopsys.com >you write:
> 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.
Right. Basically when gcc-2.7.2 has generated incorrect code they've tweaked
the asms to work around the problem. Over time they end up with a set of
asms that generally works with gcc-2.7.2.
However, that does not mean they will consistently work over time -- as the
source around the asm changes, the register allocation and reloading needs
will also change, which may again trigger problems.
jeff
WARNING: multiple messages have this Message-ID
From: Jeffrey A Law <law@hurl.cygnus.com>
To: Joe Buck <jbuck@Synopsys.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: <29536.921094521@hurl.cygnus.com> (raw)
Message-ID: <19990331234600.MDQ4H2j_hJ6CLpUD2wBRJ7vah8Y0-yQf1M3KL7QujI4@z> (raw)
In-Reply-To: <199903101931.LAA02190@atrus.synopsys.com>
In message < 199903101931.LAA02190@atrus.synopsys.com >you write:
> 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.
Right. Basically when gcc-2.7.2 has generated incorrect code they've tweaked
the asms to work around the problem. Over time they end up with a set of
asms that generally works with gcc-2.7.2.
However, that does not mean they will consistently work over time -- as the
source around the asm changes, the register allocation and reloading needs
will also change, which may again trigger problems.
jeff
next prev parent reply other threads:[~1999-03-10 11:35 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
[not found] ` < 199903101931.LAA02190@atrus.synopsys.com >
1999-03-10 11:35 ` Jeffrey A Law [this message]
[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=29536.921094521@hurl.cygnus.com \
--to=law@hurl.cygnus.com \
--cc=egcs@egcs.cygnus.com \
--cc=jbuck@Synopsys.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).