public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Vijay <vijay@nii.ac.jp>
To: gcc-help@gcc.gnu.org
Cc: Ian Lance Taylor <iant@google.com>
Subject: Re: Enquiry
Date: Tue, 02 Jun 2009 14:08:00 -0000	[thread overview]
Message-ID: <4A253264.1050702@nii.ac.jp> (raw)
In-Reply-To: <m363fe6a36.fsf@google.com>

  Thanks for the response. Error message I am getting in Windows (Cygwin 
shell),  I am using gcc compiler  supplied along with v850e/ma3 board. 
May I ask how to get upto date information about  gcc compiler for v850e 
(as gcc compiler is configured for v850e)?

Thanks,
-Vijay

Ian Lance Taylor wrote:
> Vijay Holimath <vijay@nii.ac.jp> writes:
>
>   
>>         I am using gcc compiler for v850e cpu. When I use the
>> arrtribute: __attribute__ ((interrupt_handler)) or __attribute__
>> ((interrupt); for interrupt function,  say for example
>>     
>
> ...
>
>   
>> I am getting following error messages when I compile:
>>
>> main.o (.text+0xea): In function 'swnmi': undefined reference to '__ep'
>>
>> main.o (.text+0xee): In function 'swnmi': undefined reference to '__ep'
>>     
>
> It looks like the compiler expects the linker to define __ep.  Make sure
> you have an up to date version of the GNU binutils.
>
> Ian
>
>   

  reply	other threads:[~2009-06-02 14:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-02 13:02 Enquiry Vijay Holimath
2009-06-02 13:26 ` Enquiry Ian Lance Taylor
2009-06-02 14:08   ` Vijay [this message]
2009-06-02 19:34 ` Enquiry Michael Meissner
2009-06-03  0:23   ` Enquiry Vijay
2009-06-04 15:32     ` Enquiry Michael Meissner
  -- strict thread matches above, loose matches on Subject: below --
2019-07-07 13:58 enquiry Manfredo di Porcia
2019-07-07 19:30 ` enquiry Jonathan Wakely
2017-10-29  4:09 Enquiry Karim Smith 
2009-06-04 10:19 Enquiry Vijay Holimath
2006-09-29 11:03 ENQUIRY Dr.Richard Lovward

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=4A253264.1050702@nii.ac.jp \
    --to=vijay@nii.ac.jp \
    --cc=gcc-help@gcc.gnu.org \
    --cc=iant@google.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).