This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils 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: Assembler messages [PATCH]


I changed the error message so that it is correct for the case that
I am seeing. I do not know if this is correct for every case.

Please cc me in your reply. Cheers!
Shaun


2004-06-10  Shaun Jackman  <sjackman@debian.org>

	* gas/config/tc-arm.c (tc_gen_reloc): Provide a descriptive error
	message when a PC relative relocation is out of range.

--- tc-arm.c-   2004-05-17 12:36:08.000000000 -0700
+++ tc-arm.c    2004-06-10 17:09:42.000000000 -0700
@@ -12830,7 +12830,8 @@
        }

       as_bad_where (fixp->fx_file, fixp->fx_line,
-                   _("internal_relocation (type: OFFSET_IMM) not fixed up"));
+             _("symbol `%s' is out of range (4096 bytes from the program counter)"),
+             S_GET_NAME (fixp->fx_addsy));
       return NULL;

     default:


On Thu June 10, 2004 07h42, you wrote:
> Hi Shaun,
>
> > ../../arch-at91/syscall_handler.S: Assembler messages:
> > ../../arch-at91/syscall_handler.S:25: Error: internal_relocation
> > (type: OFFSET_IMM) not fixed up
> >
> > ... and line 25 says...
> > 	ldr lr, syscall_lr
> >
> > ... which I think means that syscall_lr is out of range. So if
> > I'm correct, my wish-list item requests that this error message
> > state why the fix-up failed (presumably because this memory
> > address is out of range), what the range is, and by what amount
> > the range was exceeded.
>
> Please feel free to submit a patch that does this.
>
> Cheers
> 	 Nick


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