public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: suzhe@turbolinux.com.cn
To: gcc-gnats@gcc.gnu.org
Subject: ada/8837: (was 8814) GCC 3.2.1 generates wrong code when compiling linux kernel for Intel StrongARM SA1110 Assabet Development board.
Date: Thu, 05 Dec 2002 17:26:00 -0000	[thread overview]
Message-ID: <20021206011704.27417.qmail@sources.redhat.com> (raw)


>Number:         8837
>Category:       ada
>Synopsis:       (was 8814) GCC 3.2.1 generates wrong code when compiling linux kernel for Intel StrongARM SA1110 Assabet Development board.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Dec 05 17:26:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     suzhe@turbolinux.com.cn
>Release:        3.2.1
>Organization:
>Environment:
Host Linux with gcc 3.2 and 2.95.3 (tried both). target is an Intel StrongARM SA1110 Assabet Development board. the version of binutils is 2.13.1.
>Description:
You may download the objdump result of two kernel binary at:

http://www.gnuchina.org/~suzhe/vmlinux-asm.tar.bz2

gcc 2.95.2 version is OK. But gcc 3.2.1 version cannot boot.

kernel compiled with gcc 3.2.1 freezed at the first syscall (clone) when execute init kernel thread. I traced into the kernel and found that the syscall (clone) in kernel_thread function has no effect. I knew little about ARM asm language, so I cannot point out which code section is wrong. But I guess we can focus on kernel_thread and vector_swi functions.

http://www.gnuchina.org/~suzhe/vmlinux-asm.tar.bz2
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2002-12-06  1:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20021206011704.27417.qmail@sources.redhat.com \
    --to=suzhe@turbolinux.com.cn \
    --cc=gcc-gnats@gcc.gnu.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 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).