This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: How to force gcc to long-call a function (on MIPS)?

From: David Daney <ddaney at avtrex dot com>
To: PRC <panruochen at gmail dot com>
Cc: Andrew Haley <aph at redhat dot com>, gcc-help <gcc-help at gcc dot gnu dot org>
Date: Fri, 22 Feb 2008 09:58:35 -0800
Subject: Re: How to force gcc to long-call a function (on MIPS)?
References: <200802211606232467005@gmail.com>, <47BD5805.1020402@redhat.com>, <200802212008221576208@gmail.com>, <47BD6B67.5080708@redhat.com> <200802212044127743019@gmail.com>

PRC wrote:
> Hi Andrew,
> 
> Declaring `extern int func_addr(int)' with `-mlong-calls' sloves my problem.
> Simply declaring `extern int func_addr(int) __attribute__((long_call))' without `-mlong-calls' does not.
> 

You don't say what version of gcc you are using.  It may be worth while
to upgrade to GCC-4.3 ( available as  a release candidate right now).

David Daney

Follow-Ups:
- Re: Re: How to force gcc to long-call a function (on MIPS)?
  - From: PRC
- Re: Re: How to force gcc to long-call a function (on MIPS)?
  - From: PRC

References:
- How to force gcc to long-call a function (on MIPS)?
  - From: PRC
- Re: How to force gcc to long-call a function (on MIPS)?
  - From: Andrew Haley
- Re: Re: How to force gcc to long-call a function (on MIPS)?
  - From: PRC
- Re: How to force gcc to long-call a function (on MIPS)?
  - From: Andrew Haley
- Re: Re: How to force gcc to long-call a function (on MIPS)?
  - From: PRC

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]