From: Scott Robert Ladd <lkml@coyotegulch.com>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Has anyone had problems with GCC 4.0 and the kernel?
Date: Thu, 09 Jun 2005 11:50:39 -0400 [thread overview]
Message-ID: <42A8654F.1020500@coyotegulch.com> (raw)
In-Reply-To: <17064.22132.219886.207366@alkaid.it.uu.se>
Mikael Pettersson wrote:
> gcc-4.0.0 vanilla is broken and miscompiles some ipv4/sysctl stuff.
> More recent 4.0.1 snapshots are OK.
They're rolling release candidates for GCC 4.0.1 at the moment, so I
expect it to be out early next week. I'll simply recommend people wait
for the 4.0.1 release.
I get 2-3 messages per day, steadily, from people with various kernel
and GCC problems. Since I'm not exactly a kernel developer, I wonder why
they think *I* have answers.
Must be Google's fault... ;)
..Scott
next prev parent reply other threads:[~2005-06-09 15:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-09 14:21 Has anyone had problems with GCC 4.0 and the kernel? Scott Robert Ladd
2005-06-09 14:47 ` Mikael Pettersson
2005-06-09 15:50 ` Scott Robert Ladd [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-09 21:20 Nick Warne
2005-06-11 19:32 ` Adrian Bunk
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=42A8654F.1020500@coyotegulch.com \
--to=lkml@coyotegulch.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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