public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: ali hagigat <hagigatali@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: .text, .data and .bbs!!
Date: Mon, 06 Dec 2010 23:19:00 -0000	[thread overview]
Message-ID: <mcrfwuav6a1.fsf@google.com> (raw)
In-Reply-To: <AANLkTiki3=hHvnMVkZ6P-CkHQ7hXo50hO_7oeWh+e6XU@mail.gmail.com>	(ali hagigat's message of "Sat, 4 Dec 2010 14:48:01 +0330")

ali hagigat <hagigatali@gmail.com> writes:

> I want to write a C or Assembly program and compile it by GNU GCC. Is
> it possible to compile(or assemble) the code so that the final object
> code does not have any .text, .data and .bss sections?
> Generating these sections are compulsory by GCC?

It's not gcc, but the GNU assembler, which always creates those
sections.  And the GNU assembler does always create those sections;
I don't know of any way to disable that.

Ian

      reply	other threads:[~2010-12-06 23:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-04 11:18 ali hagigat
2010-12-06 23:19 ` 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=mcrfwuav6a1.fsf@google.com \
    --to=iant@google.com \
    --cc=binutils@sourceware.org \
    --cc=hagigatali@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).