All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Soete <joel.soete@freebel.net>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: xam@cs.ucc.ie, parisc-linux@lists.parisc-linux.org,
	bruno_vidal@hpfrcu03.france.hp.com
Subject: Re: [parisc-linux] PA8000 modutils problems
Date: Sun, 23 Jun 2002 11:55:27 +0000	[thread overview]
Message-ID: <3D15B72F.2080403@freebel.net> (raw)
In-Reply-To: 200206221953.g5MJrIHe000465@hiauly1.hia.nrc.ca

Dave,

The problem mentionned in this mail:
http://lists.parisc-linux.org/pipermail/parisc-linux/2002-April/016119.html

about gcc-3.2 is the same with gcc-3.1.

Dono about some follow-up?

Thanks for advise,
	Joel

PS:
What means PR (how to fil it)?
And what means insn?

John David Anglin wrote:
>>Some weeks ago I also try to compile the kernel (32bits) with gcc-3.1 
>>(cvs) and eventhought it boots fine there was a problem
>>with network connections (as well telnet which uses inetd as well as ssh
>>which using its own sshd; this confirm the problem of compilation in 
>>network interface). Is this problem solved now?
> 
> 
> Not that I am aware of.  Maybe some of the debian folks have tried looking
> into it as they were talking about moving to a newer compiler release.  
> If it is a compiler problem, I would need a test case showing the
> miscompilation and preferably a filed PR.
> 
> Dave

  reply	other threads:[~2002-06-23 11:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-21 20:52 [parisc-linux] PA8000 modutils problems M. Grabert
2002-06-21 21:25 ` John David Anglin
2002-06-21 22:51   ` M. Grabert
2002-06-22  1:39     ` John David Anglin
2002-06-22 18:05   ` Joel Soete
2002-06-22 19:53     ` John David Anglin
2002-06-23 11:55       ` Joel Soete [this message]
2002-06-22  2:05 ` Grant Grundler
2002-06-24  0:01   ` M. Grabert
2002-06-24  2:13 ` Applied GNU GPL virus was " M. Grabert
2002-06-24  4:23   ` John David Anglin
2002-06-24 13:50   ` Grant Grundler

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=3D15B72F.2080403@freebel.net \
    --to=joel.soete@freebel.net \
    --cc=bruno_vidal@hpfrcu03.france.hp.com \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=xam@cs.ucc.ie \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.