From: Jakub Jelinek <jakub@redhat.com>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: ppc32 weirdness with gcc-4.0 in 2.6.11-rc4
Date: Thu, 24 Feb 2005 11:01:39 -0500 [thread overview]
Message-ID: <20050224160139.GF853@devserv.devel.redhat.com> (raw)
In-Reply-To: <16925.60927.49095.758660@alkaid.it.uu.se>
On Thu, Feb 24, 2005 at 04:08:47PM +0100, Mikael Pettersson wrote:
> _However_, the 0k data message is due to a gcc-4.0 bug, and below
> you'll find a test program which illustrates it.
http://gcc.gnu.org/PR20196
Jakub
next prev parent reply other threads:[~2005-02-24 16:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-23 20:28 ppc32 weirdness with gcc-4.0 in 2.6.11-rc4 Mikael Pettersson
2005-02-24 2:04 ` Benjamin Herrenschmidt
2005-02-24 15:08 ` Mikael Pettersson
2005-02-24 15:37 ` Jakub Jelinek
2005-02-24 16:01 ` Jakub Jelinek [this message]
2005-02-25 10:08 ` Mikael Pettersson
2005-02-25 14:27 ` Mikael Pettersson
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=20050224160139.GF853@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).