public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@panasas.com>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix extern inline errors with gcc 4.3.0
Date: Sun, 29 Jun 2008 10:32:43 +0300	[thread overview]
Message-ID: <48673A9B.8050907@panasas.com> (raw)
In-Reply-To: <7225594ED4A1304C9E43D030A886D221050BE1@daytona.int.panasas.com>

On Jun. 28, 2008, 16:10 +0300, "Halevy, Benny" <bhalevy@panasas.com> wrote:
> On Fri 2008-06-27 19:26, Jeff Dike <jdike@addtoit.com> wrote:
>> On Thu, Jun 26, 2008 at 04:50:51PM +0300, Benny Halevy wrote:
>>> -KBUILD_CFLAGS += $(call cc-option,-fno-unit-at-a-time,)
>>> +# Disable unit-at-a-time mode on pre-gcc-4.3 compilers, it makes gcc use
>>> +# a lot more stack due to the lack of sharing of stacklots:
>>> +# gcc 4.3.0 needs -funit-at-a-time for extern inline functions
>>> +KBUILD_CFLAGS += $(shell if [ $(call cc-version) -lt 0403 ] ; then \
>>> +			echo $(call cc-option,-fno-unit-at-a-time); fi ;)
>> How do we know that this patch won't cause the same crash reported in
>> http://marc.info/?l=linux-kernel&m=121011722806093&w=2?

Note that the crash happened with gcc 4.1.2 and it will get the
-fno-unit-at-a-time flag with the proposed patch.

That said, this option or the lack of it ought not to cause any
runtime crashes.  If it does, I'd feel much more comfortable to know
exactly what the root cause is before deciding to use the flag to
workaround^hide it.

Benny

> 
> I don't know what was the root cause for the crash you mentioned.
> FWIW, with these options UML/x86_64 builds on Fedora 9, w/ gcc 4.3.0
> and runs well for me.
> 
> Benny
> 
>> 				Jeff
>>
>> -- 
>> Work email - jdike at linux dot intel dot com
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


  reply	other threads:[~2008-06-29  7:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-26 13:50 [PATCH] fix extern inline errors with gcc 4.3.0 Benny Halevy
2008-06-27 16:26 ` Jeff Dike
2008-06-28 13:10   ` Halevy, Benny
2008-06-29  7:32     ` Benny Halevy [this message]
2008-06-30 16:22       ` Jeff Dike
2008-06-30 16:37         ` Benny Halevy
2008-07-07 16:58           ` Jeff Dike
2008-06-30 16:43         ` Adrian Bunk
2008-08-08  1:02         ` [uml-devel] " Rob Landley
2008-08-08  1:42         ` Rob Landley

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=48673A9B.8050907@panasas.com \
    --to=bhalevy@panasas.com \
    --cc=jdike@addtoit.com \
    --cc=linux-kernel@vger.kernel.org \
    --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