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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "Andrew Haley" <aph@xxxxxxxxxx>
Subject: Re: Re: How to force gcc to long-call a function (on MIPS)?
From: "PRC" <panruochen@xxxxxxxxx>
Date: Thu, 21 Feb 2008 20:44:16 +0800
Cc: "gcc-help" <gcc-help@xxxxxxxxxxx>
References: <200802211606232467005@xxxxxxxxx>, <47BD5805.1020402@xxxxxxxxxx>, <200802212008221576208@xxxxxxxxx>, <47BD6B67.5080708@xxxxxxxxxx>

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.

>I'll ask again: Does `-mlong-calls' solve your problem?
>
>Andrew.

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

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

Prev by Date: Re: How to force gcc to long-call a function (on MIPS)?
Next by Date: g++ and templates
Previous by thread: Re: How to force gcc to long-call a function (on MIPS)?
Next by thread: Re: How to force gcc to long-call a function (on MIPS)?
Index(es):
- Date
- Thread

[Index of Archives] [Linux C Programming] [Linux Kernel] [eCos] [Fedora Development] [Fedora Announce] [Autoconf] [The DWARVES Debugging Tools] [Yosemite Campsites] [Yosemite News] [Linux GCC]

Powered by Linux