From: Adrian Bunk <bunk@kernel.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Simon Horman <horms@verge.net.au>,
linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
Stephen Tweedie <sct@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Mark McLoughlin <markmc@redhat.com>, Ingo Molnar <mingo@elte.hu>,
Jan Beulich <jbeulich@novell.com>,
Dhaval Giani <dhaval@linux.vnet.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: Allow compile with CONFIG_DEBUG_INFO=y, X86_PAE not set on gcc 3.4.5
Date: Fri, 8 Aug 2008 11:01:55 +0300 [thread overview]
Message-ID: <20080808080155.GA1992@cs181140183.pp.htv.fi> (raw)
In-Reply-To: <489BE9C3.2010006@goop.org>
On Thu, Aug 07, 2008 at 11:37:55PM -0700, Jeremy Fitzhardinge wrote:
> Simon Horman wrote:
>> Hi,
>>
>> It appears that "x86: preallocate and prepopulate separately"
>> (d8d5900ef8afc562088f8470feeaf17c4747790f) introduced a minor regression.
>> The build fails on gcc 3.4.5 if CONFIG_DEBUG_INFO=y (that is gcc is
>> called with -g) and X86_PAE not set.
>>
>> There was previously some discussion of this without resolution.
>> http://lkml.org/lkml/2008/7/18/250
>>
>> arch/x86/mm/pgtable.c: In function `pgd_prepopulate_pmd':
>> arch/x86/mm/pgtable.c:222: internal compiler error: in remove_insn, at emit-rtl.c:3746
>> Please submit a full bug report,
>> with preprocessed source if appropriate.
>> See <URL:http://gcc.gnu.org/bugs.html> for instructions.
>>
>> # i686-unknown-linux-gnu-gcc --version
>> i686-unknown-linux-gnu-gcc (GCC) 3.4.5
>>
>> My investigations seem to show that gcc 3.4.5 can't cope with the following
>> construct:
>>
>> for (i = 0; i < 0; i++)
>> ...
>>
>> or more specifically:
>>
>> for (i = 0; i < PREALLOCTED_PMDS; i++)
>> ...
>>
>> when PREALLOCTED_PMDS is 0. That is, when X86_PAE is not set.
>>
>> This patch resolves this problem by moving the relevant code inside
>> #define X86_PAE and providing dummy functions outside !X86_PAE.
>>
>> Signed-off-by: Simon Horman <horms@verge.net.au>
>>
>
> We resolved the other report by saying that gcc 3.4.4 is broken. It
> seems 3.4.5 is as well. Could you just update the compiler? I'd rather
> not have to clutter the code with more ifdefs if we can possibly avoid
> it.
>...
CONFIG_DEBUG_INFO=y is why I never hit it before.
It does not seem to be just one dodgy Redhat compiler (as I assumed in
the Bugzilla entry) but the whole 3.4 series of gcc which makes our
resolution of saying that this specific compiler is broken invalid.
Considering that we officially support all compilers >= 3.2 this is just
one more case where we have to add to the kernel a workaround for a
broken compiler.
After all, we already have 2 or 3 workarounds for new 2.6.27-rc
breakages with gcc 3.2 included or at least submitted.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-08-08 8:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 5:04 Simon Horman
2008-08-08 6:37 ` Jeremy Fitzhardinge
2008-08-08 7:50 ` Simon Horman
2008-08-08 8:01 ` Adrian Bunk [this message]
2008-08-08 15:21 ` [Xen-devel] " Jeremy Fitzhardinge
2008-08-08 16:13 ` Adrian Bunk
2008-08-08 18:01 ` Jeremy Fitzhardinge
2008-08-08 18:37 ` Adrian Bunk
2008-08-08 20:46 ` [PATCH] x86: work around gcc 3.4.x bug Jeremy Fitzhardinge
2008-08-09 6:29 ` Simon Horman
2008-08-11 16:44 ` Ingo Molnar
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=20080808080155.GA1992@cs181140183.pp.htv.fi \
--to=bunk@kernel.org \
--cc=dhaval@linux.vnet.ibm.com \
--cc=ehabkost@redhat.com \
--cc=horms@verge.net.au \
--cc=hpa@zytor.com \
--cc=jbeulich@novell.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=mingo@elte.hu \
--cc=sct@redhat.com \
--cc=tglx@linutronix.de \
--cc=xen-devel@lists.xensource.com \
/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
all inboxes | Powered by JetHome®