From: Richard Weinberger <richard@nod.at>
To: James McMechan <james_mcmechan@hotmail.com>
Cc: mikpe@it.uu.se, linux-kernel@vger.kernel.org,
uml devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] gcc-4.6.0 generates no code for sub_preempt_count()
Date: Fri, 15 Apr 2011 17:17:42 +0200 [thread overview]
Message-ID: <201104151717.42534.richard@nod.at> (raw)
In-Reply-To: <COL101-W165ED5CB17434202CE273DE2AD0@phx.gbl>
Am Donnerstag 14 April 2011, 21:50:13 schrieb James McMechan:
> > > > Any ideas whether this is a gcc or a kernel issue?
>
> It looks like a gcc error with one of the optimization passes
I've submitted a bug report.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48623
Thanks,
//richard
next prev parent reply other threads:[~2011-04-15 15:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 19:50 gcc-4.6.0 generates no code for sub_preempt_count() Richard Weinberger
2011-04-14 7:49 ` Mikael Pettersson
2011-04-14 13:52 ` Richard Weinberger
2011-04-14 19:50 ` [uml-devel] " James McMechan
2011-04-15 15:17 ` Richard Weinberger [this message]
2011-04-14 14:43 ` masterkom masterkom
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=201104151717.42534.richard@nod.at \
--to=richard@nod.at \
--cc=james_mcmechan@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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