public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: pingved@gmail.com
Cc: gcc-help@gcc.gnu.org
Subject: Re: gcc: x86: using fs and gs.
Date: Thu, 23 Apr 2009 21:00:00 -0000	[thread overview]
Message-ID: <m3y6tr2igw.fsf@google.com> (raw)
In-Reply-To: <108902202.20090423151235@gmail.com> (pingved@gmail.com's message of "Thu\, 23 Apr 2009 15\:12\:35 +0400")

pingved@gmail.com writes:

> How i can generate executable file with using FS and GS for dedicated ROM
> object with gcc for x86?

gcc does not currently support this in general.  It does use FS and GS
for the special case of TLS, but I doubt that will work for your
purposes.

There is some development work on named addresses which might be able to
support this kind of thing some day.

Ian

      reply	other threads:[~2009-04-23 21:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23 11:05 pingved
2009-04-23 21:00 ` Ian Lance Taylor [this message]

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=m3y6tr2igw.fsf@google.com \
    --to=iant@google.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=pingved@gmail.com \
    /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).