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: Re: How to force gcc to long-call a function (on MIPS)?

From: "PRC" <panruochen at gmail dot com>
To: "David Daney" <ddaney at avtrex dot com>
Cc: "Andrew Haley" <aph at redhat dot com>, "gcc-help" <gcc-help at gcc dot gnu dot org>
Date: Sun, 24 Feb 2008 18:06:14 +0800
Subject: Re: 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>, <47BF0D4B.6020001@avtrex.com>

1). Declaring `extern int func_entry(int) __attribute__((far))' without `-mlong-calls' is okay.
2). Declaring `extern int func_entry(int) __attribute__((long_call))' without `-mlong-calls' is not okay.
3). Declaring `extern char func_entry[]' and `typedef int (*FUNC_ENTRY)(int) __attribute__((far))', and calling it by ` ((FUNC_ENTRY)func_entry)(para) ' without `-mlong-calls' is not okay either, even if this usage is semantically equal to usage 1.

I am not sure either this is a bug of gcc or this is a misusage of __attribute__((far))/__attribute__((long_call)).

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
- Re: How to force gcc to long-call a function (on MIPS)?
  - From: David Daney

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