public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zack@rabi.columbia.edu>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: egcs@egcs.cygnus.com
Subject: Re: egcs and Linux kernels
Date: Wed, 31 Mar 1999 23:46:00 -0000	[thread overview]
Message-ID: <199903101527.KAA15375@blastula.phys.columbia.edu> (raw)
Message-ID: <19990331234600.o1tHNIR-ISZBVQf1nSImeYOLqW0qG8QTF1HczZVZl1g@z> (raw)
In-Reply-To: <Pine.BSF.4.10.9903101606330.44575-100000@alkaid.dbai.tuwien.ac.at>

On Wed, 10 Mar 1999 16:12:50 +0100 (CET), Gerald Pfeifer wrote:
>As I'm not a Linux expert, could someone please help with a FAQ entry
>concerning egcs and Linux kernels?
>
> o Specifically, which version/release of Linux works with which
>   version/release of egcs?
>
> o Even more specifically, how is the situation between egcs 1.1.2 and
>   Linux 2.2.x kernels?

My understanding, which should be confirmed by someone else, such as
Bernd Schmidt:

- 2.0.x and prior kernels should only be compiled with gcc 2.7.x.
- 2.2.x is expected to work with any version of egcs.

- gcc 2.8.1 and egcs (all released versions) may silently generate bad
code for the incorrect asm constructs in old kernels 
- egcs development snapshots will error out rather than accept them.

I'm typing this on a box running 2.2.1 compiled by 1.1.1, which has
had no problems, but it doesn't have any exotic hardware or SMP or
anything.

zw

  reply	other threads:[~1999-03-31 23:46 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 [this message]
     [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
     [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=199903101527.KAA15375@blastula.phys.columbia.edu \
    --to=zack@rabi.columbia.edu \
    --cc=egcs@egcs.cygnus.com \
    --cc=pfeifer@dbai.tuwien.ac.at \
    /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).