From: Paul Koning <pkoning@xedia.com>
To: law@cygnus.com
Cc: egcs@cygnus.com, torvalds@transmeta.com
Subject: Re: Linux and EGCS
Date: Mon, 15 Dec 1997 12:14:00 -0000 [thread overview]
Message-ID: <9712152013.AA22432@kona.> (raw)
In-Reply-To: <28786.882200973@hurl.cygnus.com>
>>>>> "Jeffrey" == Jeffrey A Law <law@hurl.cygnus.com> writes:
>...
Jeffrey> Can you try this change and let me know if it fixes your
Jeffrey> problems? If so I'd like to include it in egcs-1.0.1.
Looks good. In the mips testcase it has the right effect (i.e.,
"volatile" is no longer needed in asm statements with no outputs, the
resulting .s file is the same either way (except, curiously, for the
fact that a lot of labels have different numbers...).
I also rebuilt my Linux kernel and it runs, though the real test of
that will take longer.
paul
next prev parent reply other threads:[~1997-12-15 12:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9712121715.AA19735@kona.>
1997-12-15 7:49 ` Jeffrey A Law
1997-12-15 12:14 ` Paul Koning [this message]
1997-12-15 17:27 Peter Schmid
1997-12-15 18:25 ` Richard Henderson
1997-12-15 22:21 ` Jeffrey A Law
[not found] <9712101650.AA16396@kona.>
1997-12-10 10:58 ` Linus Torvalds
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=9712152013.AA22432@kona. \
--to=pkoning@xedia.com \
--cc=egcs@cygnus.com \
--cc=law@cygnus.com \
--cc=torvalds@transmeta.com \
/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).