Message-ID: <49F9D1E5.2090805@zytor.com>
Date: Thu, 30 Apr 2009 09:29:25 -0700
From: "H. Peter Anvin" <hpa@zytor.com>
User-Agent: Thunderbird 2.0.0.14 (X11/20080501)
MIME-Version: 1.0
To: Sam Ravnborg <sam@ravnborg.org>
CC: mingo@redhat.com, linux-kernel@vger.kernel.org,
       torvalds@linux-foundation.org, tglx@linutronix.de, jdb@comx.dk,
       mingo@elte.hu, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/kbuild] x86: boot/compressed/vmlinux.lds.S: fix build
 of bzImage with 64 bit compiler
References: <alpine.LFD.2.00.0904260958190.3101@localhost.localdomain> <tip-83c4832683bc8ebcd1687b3c0bf3ba1ab253dd4f@git.kernel.org> <49F9BB47.7080806@zytor.com> <20090430150924.GA8656@uranus.ravnborg.org>
In-Reply-To: <20090430150924.GA8656@uranus.ravnborg.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 894
Lines: 26

Sam Ravnborg wrote:
>>>
>> I'm wondering if we should build the *.lds.S with -ansi or some other
>> gcc option which disables ALL non-underscore macros.
> 
> I did not know that -ansi had this effect.
> We are only seldomly hitting this issue and I wonder
> if it could break something in out included headers.
> Most likely not.
> 

The other thing to recognize is probably that lds files aren't assembly,
they're something else entirely.  Rather than reusing the *.S rules,
having specific rules for them probably would make sense.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

--
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/