public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "samuel dot thibault at ens-lyon dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/29838] -fstack-protector shouldn't use TLS in freestanding mode
Date: Wed, 15 Nov 2006 11:01:00 -0000	[thread overview]
Message-ID: <20061115110142.13197.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29838-11603@http.gcc.gnu.org/bugzilla/>



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


  parent reply	other threads:[~2006-11-15 11:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-15  1:14 [Bug c/29838] New: " samuel dot thibault at ens-lyon dot org
2006-11-15  1:17 ` [Bug c/29838] " samuel dot thibault at ens-lyon dot org
2006-11-15  2:50 ` [Bug target/29838] " pinskia at gcc dot gnu dot org
2006-11-15  9:33 ` samuel dot thibault at ens-lyon dot org
2006-11-15 10:11 ` tschwinge at gnu dot org
2006-11-15 10:23 ` jakub at gcc dot gnu dot org
2006-11-15 10:30 ` samuel dot thibault at ens-lyon dot org
2006-11-15 10:38 ` jakub at gcc dot gnu dot org
2006-11-15 10:41 ` jakub at gcc dot gnu dot org
2006-11-15 11:01 ` samuel dot thibault at ens-lyon dot org [this message]
2006-12-15 19:30 ` tschwinge at gnu dot org
     [not found] <bug-29838-4@http.gcc.gnu.org/bugzilla/>
2015-01-08 17:12 ` egall at gwmail dot gwu.edu

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=20061115110142.13197.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).