From: David Daney <ddaney@avtrex.com>
To: Kishore K <hellokishore@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: gcc -3.4.4 and linux-2.4.32
Date: Mon, 16 Jan 2006 09:34:19 -0800 [thread overview]
Message-ID: <43CBD91B.4020607@avtrex.com> (raw)
In-Reply-To: <f07e6e0601160423h5ce1c0d7lcb7e38f8509c4116@mail.gmail.com>
Kishore K wrote:
> hi
> When 2.4.32 kernel (from linux-mips) is compiled with the tool chain
> based on gcc 3.4.4 and binutils 2.16.1, the kernel crashes on malta
> board. The crash file is enclosed along with the mail. If the same
> kernel is compiled with the tool chain based on gcc 3.3.6, no problem is
> observed.
>
> May I know, whether it is because of the changes in ABI in gcc 3.4.
Not exactly. It has to do with -funit-at-a-time. In the 2.4.x kernel
it is assumed that gcc will not reorder top level asm statements and
functions. For gcc-3.3.x and earlier this was a valid assumption. With
3.4.x and later it is not.
> If
> so, has any one got the patch to make 2.4.x kernels work with gcc 3.4
> compilers? From the changelog, I can infer that, some changes have been
> done in 2.4.28 kernel to work with gcc 3.4 for i386. If so, has the same
> thing been done for MIPS as well.
>
IIRC the patches were never applied to linux-mips.org. If you search
the archives of this list for messages that I sent, you can find the
patches.
David Daney.
next prev parent reply other threads:[~2006-01-16 17:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 12:23 gcc -3.4.4 and linux-2.4.32 Kishore K
2006-01-16 12:23 ` Kishore K
2006-01-16 17:34 ` David Daney [this message]
2006-01-17 12:07 ` Kishore K
2006-01-17 12:26 ` P. Christeas
2006-01-18 22:35 ` P. Christeas
2006-01-19 10:00 ` Geert Uytterhoeven
2006-01-19 10:30 ` P. Christeas
2006-01-19 12:33 ` "useless" pgprot_noncached define in include/asm-mips/pgtable.h Niels Sterrenburg
2006-01-23 15:54 ` Atsushi Nemoto
2006-01-17 13:43 ` gcc -3.4.4 and linux-2.4.32 Ralf Baechle
2006-01-17 13:40 ` Ralf Baechle
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=43CBD91B.4020607@avtrex.com \
--to=ddaney@avtrex.com \
--cc=hellokishore@gmail.com \
--cc=linux-mips@linux-mips.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