All of lore.kernel.org
 help / color / mirror / Atom feed
From: Diaconescu Bogdan-BDIACON1 <bogdan.diaconescu@motorola.com>
To: Franz Sirl <Franz.Sirl-ppc@lauterbach.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: RE: Gcc longcall option
Date: Fri, 25 Jul 2003 19:14:48 +0300	[thread overview]
Message-ID: <DD38D67B9196D31189EC00508B62563701CA64B5@zro01exm01.corp.mot.com> (raw)


Thanks,
I'll try gcc-3.3 version whith the pragm you said.

Bogdan

-----Original Message-----
From: Franz Sirl [mailto:Franz.Sirl-ppc@lauterbach.com]
Sent: Thursday, July 24, 2003 2:11 PM
To: Diaconescu Bogdan-BDIACON1
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Gcc longcall option


At 17:34 22.07.2003, Diaconescu Bogdan-BDIACON1 wrote:

>Hi guys,
>
>I have a question not strictly related to kernel but more related to
>gcc and it's options.
>
>I try to create a big exe image (around 800M with symbolics) using
>gcc-2.95.x and I run into the problems of relative branch addressing
>which has only 24 bits for PPC. I know if I use some __atribute__
>((longcall)) for function prototypes the addressing is done through LR
>so it's changed to indirect branch. I was looking for options like
>-mlongcall or -mlong-calls but it seems they don't exist for PPC.
>
>Now the question: do you know a distribution in which gcc is having
>such options or do you know another way to get the link done with the
>big exe image I have?

Starting with gcc-3.3 there is "#pragma longcall (1)", so depending on
where you put this pragma, you can default your project/module/file to
longcalls.

Franz.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2003-07-25 16:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-25 16:14 Diaconescu Bogdan-BDIACON1 [this message]
     [not found] <DD38D67B9196D31189EC00508B62563701C4921F@zro01exm01.corp.m ot.com>
2003-07-24 11:11 ` Gcc longcall option Franz Sirl
  -- strict thread matches above, loose matches on Subject: below --
2003-07-22 15:34 Diaconescu Bogdan-BDIACON1
2003-07-24 10:42 ` Michel Dänzer

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=DD38D67B9196D31189EC00508B62563701CA64B5@zro01exm01.corp.mot.com \
    --to=bogdan.diaconescu@motorola.com \
    --cc=Franz.Sirl-ppc@lauterbach.com \
    --cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.