public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "malitzke at metronets dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/27528] compiling linux kernels 2.6.16.14/15 2.6.17-rc3 on powerpc (7450) get error on long exixting code
Date: Wed, 10 May 2006 03:05:00 -0000 [thread overview]
Message-ID: <20060510030456.18703.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27528-11706@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from malitzke at metronets dot com 2006-05-10 03:04 -------
There are similar problems with other kernel modules that did not occur before.
It looks like the asm expansion causes problems with some rs6000 work done by
David Edelsohn. Will be glad to assist in solving this hopefully minor item.
Had a Hell of a time with the known to work fail fields. There should be a way
to qualify current versus twoo weeks before
--
malitzke at metronets dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to fail| |4.2.0
Known to work| |3.4.6
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27528
next prev parent reply other threads:[~2006-05-10 3:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 2:44 [Bug c/27528] New: " malitzke at metronets dot com
2006-05-10 3:05 ` malitzke at metronets dot com [this message]
2006-05-10 4:04 ` [Bug middle-end/27528] " pinskia at gcc dot gnu dot org
2006-05-10 5:24 ` pinskia at gcc dot gnu dot org
2006-05-10 5:30 ` pinskia at gcc dot gnu dot org
2006-05-10 14:44 ` malitzke at metronets dot com
2006-05-10 14:56 ` dje at gcc dot gnu dot org
2006-05-10 15:06 ` pinskia at gcc dot gnu dot org
2006-05-10 20:17 ` malitzke at metronets dot com
2006-05-10 20:41 ` pinskia at gcc dot gnu dot org
2006-06-14 15:09 ` hp at gcc dot gnu dot org
2006-06-14 15:09 ` hp at gcc dot gnu dot org
2006-06-15 3:26 ` malitzke at metronets dot com
2006-06-15 17:15 ` hp at gcc dot gnu dot org
2006-06-15 23:03 ` malitzke at metronets dot com
2006-06-15 23:03 ` Andrew Pinski
2006-06-15 23:07 ` pinskia at physics dot uc dot edu
2006-10-27 5:24 ` pinskia at gcc dot gnu dot org
2006-11-03 13:23 ` rsandifo at gcc dot gnu dot org
2006-11-03 13:27 ` hp at gcc dot gnu dot org
2006-11-03 13:30 ` rsandifo at gcc dot gnu dot org
2006-11-09 9:34 ` rsandifo at gcc dot gnu dot org
2006-11-11 9:47 ` rsandifo at gcc dot gnu dot org
2006-11-11 9:53 ` rsandifo at gcc dot gnu dot org
2006-11-11 9:54 ` rsandifo at gcc dot gnu dot org
2006-12-01 1:07 ` chaoyingfu at gcc dot gnu dot org
2007-01-10 19:14 ` [Bug middle-end/27528] [4.2/4.3 Regression] " pinskia at gcc dot gnu dot org
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=20060510030456.18703.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).