All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: "T. Weyergraf" <kirk@colinet.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.73 on alpha/smp build failure
Date: Mon, 30 Jun 2003 09:42:59 +0400	[thread overview]
Message-ID: <20030630054259.GC17466@namesys.com> (raw)
In-Reply-To: <20030629155616.B694@pls.park.msu.ru>

[-- Attachment #1: Type: text/plain, Size: 1134 bytes --]

Hello!

On Sun, Jun 29, 2003 at 03:56:16PM +0400, Ivan Kokshaysky wrote:

> > When I compile the kernel the alpha itself (tried shipped suse 8.1 gcc 3.2.2
> > and self-compiled gcc 2.95.3), it jumps to the address zero quickly after
> > launching init and panics.
> Most likely it's binutils problem. Versions 2.13.90.0.18 and newer
> should be OK, as discussed recently on l-k.

I have :
$ alphaev56-unknown-linux-gnu-size -V
GNU size 2.14 20030612
Copyright 2002 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License.  This program has absolutely no warranty.

Also I tried to compare assembly output of native vs crosscompiler and have found the result to be
different substantionally (unfortunatelly I cannot understand alpha assembly, but I see the
code looks different in the beginning. Also assembly file generated by cross-gcc produces
wrong result after translated/linked using native binutils). I assume that binutils are not involved in
"gcc -S" process.

See attached assembly generated by cross compiler vs native compiler.

Bye,
    Oleg

[-- Attachment #2: test-cross.s --]
[-- Type: text/plain, Size: 581 bytes --]

	.file	1 "test.c"
	.set noat
	.set noreorder
	.arch ev56
.section	.rodata
$LC0:
	.ascii "vs-500: unknown uniqueness %d\12\0"
$LC1:
	.ascii "result is %d\12\0"
.text
	.align 5
	.globl main
	.ent main
main:
	.frame $30,0,$26,0
	.mask 0x4000000,0
	ldgp $29,0($27)
$main..ng:
	lda $30,-16($30)
	lda $16,$LC0
	lda $17,-2
	stq $26,0($30)
	.prologue 1
	zapnot $17,15,$17
	jsr $26,printf
	ldgp $29,0($26)
	nop
	lda $16,$LC1
	lda $17,15
	jsr $26,printf
	ldgp $29,0($26)
	ldq $26,0($30)
	mov $31,$0
	lda $30,16($30)
	ret $31,($26),1
	.end main
	.ident	"GCC: (GNU) 2.95.3 20010315 (release)"

[-- Attachment #3: test-native.s --]
[-- Type: text/plain, Size: 500 bytes --]

	.file	1 "test.c"
	.set noat
	.set noreorder
	.arch ev56
.section	.rodata
$LC0:
	.ascii "vs-500: unknown uniqueness %d\12\0"
$LC1:
	.ascii "result is %d\12\0"
.text
	.align 5
	.globl main
	.ent main
main:
	.frame $30,16,$26,0
	.mask 0x4000000,-16
	ldgp $29,0($27)
$main..ng:
	lda $30,-16($30)
	lda $16,$LC1
	stq $26,0($30)
	.prologue 1
	lda $17,1
	jsr $26,printf
	ldgp $29,0($26)
	ldq $26,0($30)
	mov $31,$0
	lda $30,16($30)
	ret $31,($26),1
	.end main
	.ident	"GCC: (GNU) 2.95.3 20010315 (release)"

  reply	other threads:[~2003-06-30  5:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-28  9:28 2.5.73 on alpha/smp build failure T. Weyergraf
2003-06-28 13:38 ` Oleg Drokin
2003-06-29 11:56   ` Ivan Kokshaysky
2003-06-30  5:42     ` Oleg Drokin [this message]
2003-06-30 10:52       ` Ivan Kokshaysky
2003-06-30 11:05         ` Oleg Drokin
2003-06-29 11:45 ` Ivan Kokshaysky

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=20030630054259.GC17466@namesys.com \
    --to=green@namesys.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=kirk@colinet.de \
    --cc=linux-kernel@vger.kernel.org \
    /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.