public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: suzhe@turbolinux.com.cn To: gcc-gnats@gcc.gnu.org Subject: target/8814: GCC 3.2.1 cannot compile linux kernel 2.4.18 and 2.4.19 correctly. Date: Wed, 04 Dec 2002 17:36:00 -0000 [thread overview] Message-ID: <20021205013141.18502.qmail@sources.redhat.com> (raw) >Number: 8814 >Category: target >Synopsis: GCC 3.2.1 cannot compile linux kernel 2.4.18 and 2.4.19 correctly. >Confidential: no >Severity: critical >Priority: medium >Responsible: unassigned >State: open >Class: wrong-code >Submitter-Id: net >Arrival-Date: Wed Dec 04 17:36:00 PST 2002 >Closed-Date: >Last-Modified: >Originator: suzhe@turbolinux.com.cn >Release: 3.2.1 >Organization: >Environment: Linux cross compiler environment with gcc-3.2.1 and glibc-2.3.1 for StrongARM. >Description: Kernel compiled by gcc-3.2.1 cannot boot. I found that the system call cannot be invoked correctly. The target code generated by gcc-2.95.2 and gcc-3.2.1 are different. You can get the asm code of target kernels at: http://www.gnuchina.org/~suzhe/vmlinux-asm.tar.bz2 >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-12-05 1:36 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-04 17:36 suzhe [this message] 2002-12-05 3:24 rearnsha
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=20021205013141.18502.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: linkBe 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).