From: FX MOREL <fxmorel.gcc@gmail.com>
To: Anthony Green <green@moxielogic.com>
Cc: gcc@gcc.gnu.org
Subject: Re: [LM-32] Code generation for address loading
Date: Wed, 26 Feb 2014 11:53:00 -0000 [thread overview]
Message-ID: <CA+x5mr8b-EJxucYsEA5vhYa9n8T9S3psOsdBfZVupJtf4nkBQA@mail.gmail.com> (raw)
In-Reply-To: <87ios4xddt.fsf@moxielogic.com>
On Tue, Feb 25, 2014 at 1:08 AM, Anthony Green <green@moxielogic.com> wrote:
>
> Have you considered doing this through custom GNU linker relaxation
> work? I would try this before hacking away at the compiler.
>
> AG
>
>
This a very good idea indeed, I wasn't aware of this feature.
I will give it a try based on other relaxations done for other platforms...
Thank you for your input and I will let you know if I have any success
FX
prev parent reply other threads:[~2014-02-26 11:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 14:05 FX MOREL
2014-02-25 0:09 ` Anthony Green
2014-02-26 11:53 ` FX MOREL [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=CA+x5mr8b-EJxucYsEA5vhYa9n8T9S3psOsdBfZVupJtf4nkBQA@mail.gmail.com \
--to=fxmorel.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=green@moxielogic.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).