All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Marmond <fmarmond@eprocess.fr>
To: ruxyz@yahoo.com, linux-assembly@vger.kernel.org
Subject: Re: Prblem with AT&T
Date: Thu, 08 Aug 2002 10:02:53 +0200	[thread overview]
Message-ID: <3D5225AD.3000302@eprocess.fr> (raw)
In-Reply-To: 20020808073133.53517.qmail@web14505.mail.yahoo.com

hi!

how are you today?
;-)

well, with your error code, I think that what i said yesterday was right:
your syntax at

mymsg: 
	.byte 13,10 
	.ascii "Handling BIOS interrupts"

[...]

	movw $mymsg,%bp 

But as I don't know about At&t syntax, here is an example of good syntax

$ cat write.s
.data
hw:
	.string "hello world\n"
.text
.globl main
main:
	movl	$SYS_write,%eax
	movl	$1,%ebx
	movl	$hw,%ecx
	movl	$12,%edx
	int	$0x80
	movl	$SYS_exit,%eax
	xorl	%ebx,%ebx
	int	$0x80
	ret


For At&t / intel syntax, please refer to:
www.linuxassembly.org
or more precisely:
http://www.linuxassembly.org/linasm.html


happy new year!

;-)
Fred


Anticipating a Reply wrote:

>Hi All !
>
>  I have got the below 16 bit code which is 
>in Intel Syntax . 
>
>----------- INTEL SYNTAX CODE ------------------------
>
>entry start 
>
>start: 
>	mov ah,#0x03 ; read cursor position. 
>	xor bh,bh 
>	int 0x10 
>	mov cx,#26 ; length of our beautiful string. 
>	mov bx,#0x0007 ; page 0, attribute 7 (normal) 
>	mov bp,#mymsg 
>	mov ax,#0x1301 ; write string, move cursor 
>	int 0x10 
>	
>	loop1: jmp loop1 
>	
>mymsg: 
>	.byte 13,10 
>	.ascii "Handling BIOS interrupts"
>
>
>---------------------------------------------
>
>I am trying to write to the above code in 
>AT&T format as given below . 
>
> But I get the error in "ld" . 
>
>sect2.o: In function `_start':
>sect2.o(.text+0xd): relocation truncated to fit:
>R_386_16 data
>
>  
>-------------AT&T SYNTAX --------------------
>
>
>.code16
>
>.align 4
>
>.data
>
>mymsg: 
>	.byte 13,10 
>	.ascii "Handling BIOS interrupts"
>
>.text
>
>.globl _start 
>
>_start: 
>	movb $0x03,%ah   # read cursor position. 
>	xor  %bh,%bh
> 
>	int  $0x10 
>
>	movw $24,%cx     # length of our beautiful string. 
>	movw $0x0007,%bx # page 0, attribute 7 (normal) 
>	movw $mymsg,%bp 
>	movw $0x1301,%ax # write string, move cursor 
>
>	int  $0x10 
>	
>loop1: 
>        jmp loop1 
>	
>----------------------------------------------
>
>   Please help me how to resolve this .
>
>Regards 
>
>________________________________________________________________________
>Want to sell your car? advertise on Yahoo Autos Classifieds. It's Free!!
>       visit http://in.autos.yahoo.com
>-
>To unsubscribe from this list: send the line "unsubscribe linux-assembly" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>  
>




  reply	other threads:[~2002-08-08  8:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-08  7:31 Prblem with AT&T Anticipating a Reply
2002-08-08  8:02 ` Frederic Marmond [this message]
2002-08-08  9:28   ` Anticipating a Reply
2002-08-08 16:04 ` Maciej Hrebien
2002-08-10  4:41   ` Anticipating a Reply
2002-08-10 11:47     ` Maciej Hrebien
2002-08-10 19:35     ` Maciej Hrebien
2002-08-14  6:35       ` Anticipating a Reply
2002-08-14 18:40         ` Maciej Hrebien
2002-08-16  4:55           ` Anticipating a Reply

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=3D5225AD.3000302@eprocess.fr \
    --to=fmarmond@eprocess.fr \
    --cc=linux-assembly@vger.kernel.org \
    --cc=ruxyz@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.