From: Jakub Jelinek <jakub@redhat.com>
To: Paul Clements <Paul.Clements@SteelEye.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: gcc bug causing problem in kernel builds
Date: Thu, 23 Aug 2001 16:55:26 -0400 [thread overview]
Message-ID: <20010823165526.F4385@devserv.devel.redhat.com> (raw)
In-Reply-To: <3B855C19.7A4233BF@SteelEye.com>
In-Reply-To: <3B855C19.7A4233BF@SteelEye.com>; from Paul.Clements@SteelEye.com on Thu, Aug 23, 2001 at 03:40:09PM -0400
On Thu, Aug 23, 2001 at 03:40:09PM -0400, Paul Clements wrote:
> Does anyone know if the structure misalignment problem in gcc 2.96 is a
> known issue? (could this bug be induced by a RedHat-applied gcc patch,
> if there are any)
There are some patches applied (something like ~350 patches), but as
gcc 3.0.1 and gcc CVS head behave the same way as gcc-2.96-RH, it is not RH
specific.
Looking into it.
Jakub
prev parent reply other threads:[~2001-08-23 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-23 19:40 gcc bug causing problem in kernel builds Paul Clements
2001-08-23 20:00 ` Alan Cox
2001-08-23 20:04 ` Paul Clements
2001-08-23 20:55 ` Jakub Jelinek [this message]
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=20010823165526.F4385@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=Paul.Clements@SteelEye.com \
--cc=linux-kernel@vger.kernel.org \
/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