From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13280 invoked by alias); 15 Nov 2006 11:01:54 -0000 Received: (qmail 13198 invoked by uid 48); 15 Nov 2006 11:01:42 -0000 Date: Wed, 15 Nov 2006 11:01:00 -0000 Message-ID: <20061115110142.13197.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/msg01386.txt.bz2 List-Id: ------- Comment #9 from samuel dot thibault at ens-lyon dot org 2006-11-15 11:01 ------- About not using -fstack-protector, the problem is that it is the default on ubuntu for instance. That would mean we have to explicitely use -fno-stack-protector, but only for recent versions of gcc, so we'll have to detect that, etc... Not counting all such new options that may arise which we'd have to disable... Please answer this, at least by just yes/no: you're saying that -ffreestanding doesn't mean "an OS kernel" (as manual says), but "the kernel of the target", so that people working on other kernels will have to first build a cross-compiler? (the bug is a documentation bug then) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29838