public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Trevor Scroggins <trevor.scroggins@gmail.com>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc@gcc.gnu.org
Subject: Re: CONSTANT_POOL_BEFORE_FUNCTION has no effect in tm.h?
Date: Mon, 06 Jul 2009 17:11:00 -0000	[thread overview]
Message-ID: <ca05b9360907061011u7213fa1bo1ecd3b05045f8257@mail.gmail.com> (raw)
In-Reply-To: <m3iqi5lpa9.fsf@google.com>

The target doesn't use ELF. I have .text, .data, and .bss, and
read-only data normally goes in .text. I'm learning as I go, so I'll
fiddle with a dummy .rodata section of some sort that the linker can
position accordingly.

On Mon, Jul 6, 2009 at 10:00 AM, Ian Lance Taylor<iant@google.com> wrote:
> Most targets put constant strings and the like in the .rodata section.
> Then the linker script can put that in a useful place.  That seems like
> the best approach to use for a processor like m68k which supports
> general addressing.  I'm surprised that doesn't happen already.  I
> assume you are using an ELF target, in which case I would expect
> default_elf_select_rtx_section to do the right thing.
>
> Ian
>

  reply	other threads:[~2009-07-06 17:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-05 20:56 Trevor Scroggins
2009-07-06  6:14 ` Ian Lance Taylor
2009-07-06 16:29   ` Trevor Scroggins
2009-07-06 17:01     ` Ian Lance Taylor
2009-07-06 17:11       ` Trevor Scroggins [this message]
2009-07-06 18:29         ` Trevor Scroggins
2009-07-06 18:45           ` Ian Lance Taylor
2009-07-10 22:19             ` Trevor Scroggins
2009-07-10 22:20               ` Fwd: " Trevor Scroggins
2009-07-10 23:38               ` Ian Lance Taylor
2009-07-10 23:48                 ` Trevor Scroggins

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=ca05b9360907061011u7213fa1bo1ecd3b05045f8257@mail.gmail.com \
    --to=trevor.scroggins@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=iant@google.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).