From: "John W. Linville" <linville@tuxdriver.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, David Miller <davem@davemloft.net>,
LKML <linux-kernel@vger.kernel.org>,
"Luis R. Rodriguez" <lrodriguez@atheros.com>
Subject: Re: linux-next: wireless-current tree build failure
Date: Tue, 5 Aug 2008 12:00:26 -0400 [thread overview]
Message-ID: <20080805160026.GA14186@tuxdriver.com> (raw)
In-Reply-To: <20080805153757.GB22895@cs181140183.pp.htv.fi>
On Tue, Aug 05, 2008 at 06:37:57PM +0300, Adrian Bunk wrote:
> On Tue, Aug 05, 2008 at 04:21:52PM +1000, Stephen Rothwell wrote:
> > Hi John,
> >
> > Today's linux-next build (powerpc allyesconfig) failed like this:
> >
> > drivers/net/wireless/ath9k/hw.c: In function 'ath9k_hw_9280_spur_mitigate':
> > drivers/net/wireless/ath9k/hw.c:4660: internal compiler error: in expand_expr_real_1, at expr.c:9199
> >
> > Clearly not our fault! :-) I have informed our toolchain person. This
> > was using the Debian gcc-4.3. It also fails using the Debian 4.2
> > compiler but not the 4.1 one.
> >...
>
> Alexandros Couloumbis already opened a bug for this issue on mips, which
> also seems to be affected:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37014
>
> It is a gcc bug, but we'll have to work around it in the ath9k driver.
I imagine that we would be happy to do that. Anyone have a clue as to how?
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2008-08-05 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 6:21 linux-next: wireless-current tree build failure Stephen Rothwell
2008-08-05 15:37 ` Adrian Bunk
2008-08-05 16:00 ` John W. Linville [this message]
2008-08-05 16:35 ` Stephen Rothwell
2008-08-05 19:06 ` [2.6 patch] ath9k: work around gcc ICEs Adrian Bunk
2008-08-05 16:02 ` linux-next: wireless-current tree build failure Stephen Rothwell
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=20080805160026.GA14186@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=bunk@kernel.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=sfr@canb.auug.org.au \
/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