From: "Steven J. Hill" <sjhill@realitydiluted.com>
To: Charlie Brady <charlieb-linux-mips@e-smith.com>
Cc: "John W. Linville" <linville@lvl7.com>, linux-mips@linux-mips.org
Subject: Re: Broadcom gcc changes (was Re: Broadcom 4702?)
Date: Thu, 15 Jan 2004 15:18:49 -0500 [thread overview]
Message-ID: <4006F5A9.2040602@realitydiluted.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0401151442590.17500-100000@allspice.nssg.mitel.com>
Charlie Brady wrote:
>
> Here's some of the gcc changes, to give you all a feel for what changes
> they've made.
>
> --- gcc-3.0/gcc/config/mips/mips.h 2001-06-14 16:42:18.000000000
> -0400
> +++ WRT54G/tools-src/gnu-20010422/gcc/config/mips/mips.h 2003-10-10
> 15:15:14.000000000 -0400
> @@ -214,6 +214,7 @@
The change simply disables the compiler from emitting branch likely
instructions when compiler userspace code. Branch likely instructions
are allowed when compiling kernel code.
-Steve
next prev parent reply other threads:[~2004-01-15 20:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 22:00 Broadcom 4702? Charlie Brady
2004-01-13 22:28 ` Jun Sun
2004-01-14 20:49 ` Charlie Brady
2004-01-14 21:05 ` Jim Thompson
2004-01-14 21:15 ` Alan Cox
2004-01-14 21:42 ` Jim Thompson
2004-01-14 22:00 ` Broadcom gcc/binutils mods (Re: Broadcom 4702?) Charlie Brady
2004-01-14 22:53 ` Broadcom 4702? Alan Cox
2004-01-15 1:03 ` Jun Sun
2004-01-15 3:39 ` Charlie Brady
2004-01-15 9:11 ` Dominic Sweetman
2004-01-15 21:33 ` Alan Cox
2004-01-15 22:46 ` ilya
2004-01-14 21:50 ` Broadcom gcc/binutils changes (was Re: Broadcom 4702?) Charlie Brady
2004-01-14 21:18 ` Broadcom 4702? Jun Sun
2004-01-15 18:53 ` Charlie Brady
2004-01-15 19:14 ` John W. Linville
2004-01-15 20:08 ` Broadcom gcc changes (was Re: Broadcom 4702?) Charlie Brady
2004-01-15 20:18 ` Steven J. Hill [this message]
2004-01-15 20:25 ` John W. Linville
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=4006F5A9.2040602@realitydiluted.com \
--to=sjhill@realitydiluted.com \
--cc=charlieb-linux-mips@e-smith.com \
--cc=linux-mips@linux-mips.org \
--cc=linville@lvl7.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox