* Help! < Invalid Constant>
@ 2001-07-17 8:00 Mynampati, Venkata S.
2001-07-23 22:10 ` Alexandre Oliva
0 siblings, 1 reply; 2+ messages in thread
From: Mynampati, Venkata S. @ 2001-07-17 8:00 UTC (permalink / raw)
To: 'gcc-help@gcc.gnu.org'
Hi,
I am using gcc ver 3.0 to compile linux code.
While compiling head-armv.S file, i get this error:
head-armv.S: Assembler messages:
head-armv.S:127: Error: Invalid constant
make[1]: *** [head-armv.o] Error 1
Line 127 looks like
"add r0, r4, #(TEXTADDR - 0x8000) >> 18"
and i don;t see anything wrong with this statement.
Can you help me find out what's going on here?
Also, where can i get to see, gcc's list of error messages ?
Thanks and rgds
Venkat
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Help! < Invalid Constant>
2001-07-17 8:00 Help! < Invalid Constant> Mynampati, Venkata S.
@ 2001-07-23 22:10 ` Alexandre Oliva
0 siblings, 0 replies; 2+ messages in thread
From: Alexandre Oliva @ 2001-07-23 22:10 UTC (permalink / raw)
To: Mynampati, Venkata S.; +Cc: 'gcc-help@gcc.gnu.org'
On Jul 17, 2001, "Mynampati, Venkata S." <MynamVS@nsc-msg01.network.com> wrote:
> Line 127 looks like
> "add r0, r4, #(TEXTADDR - 0x8000) >> 18"
> and i don;t see anything wrong with this statement.
Which assembler version are you using?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2001-07-23 22:10 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-07-17 8:00 Help! < Invalid Constant> Mynampati, Venkata S.
2001-07-23 22:10 ` Alexandre Oliva
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).