public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: Mark McLoughlin <markmc@redhat.com>,
	xen-devel@lists.xensource.com,
	Eduardo Habkost <ehabkost@redhat.com>,
	Stephen Tweedie <sct@redhat.com>,
	linux-kernel@vger.kernel.org, Simon Horman <horms@verge.net.au>,
	"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
	Thomas Gleixner <tglx@linutronix.de>,
	Dhaval Giani <dhaval@linux.vnet.ibm.com>
Subject: Re: [Xen-devel] Re: Allow compile with CONFIG_DEBUG_INFO=y,	X86_PAE not set on gcc 3.4.5
Date: Fri, 08 Aug 2008 11:01:30 -0700	[thread overview]
Message-ID: <489C89FA.5000301@goop.org> (raw)
In-Reply-To: <20080808161331.GF14495@cs181140183.pp.htv.fi>

Adrian Bunk wrote:
> On Fri, Aug 08, 2008 at 08:21:41AM -0700, Jeremy Fitzhardinge wrote:
>   
>> Adrian Bunk wrote:
>>     
>>> 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.
>>>   
>>>       
>> Yes.  I'm happy to write off a specific rpm package, but a whole series  
>> is a different matter.
>>
>> Adding
>>
>> 	if (PREALLOCATED_PMDS == 0)
>> 		return;
>>
>> in the appropriate places with a small comment seems like the right answer.
>>     
>
> The patch below you suggested fixes it for me with gcc 3.4.6.
>
>   
>>    J
>>     
>
> cu
> Adrian
>   

OK.  Want to submit this as a proper patch?

Acked-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>

Thanks,
    J


>
> --- a/arch/x86/mm/pgtable.c
> +++ b/arch/x86/mm/pgtable.c
> @@ -209,6 +209,9 @@ static void pgd_prepopulate_pmd(struct mm_struct *mm, pgd_t *pgd, pmd_t *pmds[])
>  
>  	pud = pud_offset(pgd, 0);
>  
> +	if (PREALLOCATED_PMDS == 0)
> +		return;
> +
>   	for (addr = i = 0; i < PREALLOCATED_PMDS;
>  	     i++, pud++, addr += PUD_SIZE) {
>  		pmd_t *pmd = pmds[i];
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>   


  reply	other threads:[~2008-08-08 18:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-08  5:04 Allow compile with CONFIG_DEBUG_INFO=y, X86_PAE not set on gcc 3.4.5 Simon Horman
2008-08-08  6:37 ` Jeremy Fitzhardinge
2008-08-08  7:50   ` Simon Horman
2008-08-08  8:01   ` Adrian Bunk
2008-08-08 15:21     ` [Xen-devel] " Jeremy Fitzhardinge
2008-08-08 16:13       ` Adrian Bunk
2008-08-08 18:01         ` Jeremy Fitzhardinge [this message]
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=489C89FA.5000301@goop.org \
    --to=jeremy@goop.org \
    --cc=bunk@kernel.org \
    --cc=dhaval@linux.vnet.ibm.com \
    --cc=ehabkost@redhat.com \
    --cc=horms@verge.net.au \
    --cc=hpa@zytor.com \
    --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