From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4978 invoked by alias); 15 Nov 2006 10:30:41 -0000 Received: (qmail 4931 invoked by uid 48); 15 Nov 2006 10:30:23 -0000 Date: Wed, 15 Nov 2006 10:30:00 -0000 Message-ID: <20061115103023.4930.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug target/29838] -fstack-protector shouldn't use TLS in freestanding mode In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "samuel dot thibault at ens-lyon dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-11/txt/msg01383.txt.bz2 List-Id: ------- Comment #6 from samuel dot thibault at ens-lyon dot org 2006-11-15 10:30 ------- So you are saying that gcc now imposes (whatever the kernel) kernel-land and user-land to use the same TLS scheme, and now requires people to build a cross-compiler before building a kernel from another kernel's userland? I thought -ffreestanding was precisely meant to escape such considerations... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29838