From: Andreas Oberritter <obi@opendreambox.org>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/1] MIPS/MIPS32 tune -> MIPS
Date: Tue, 10 Apr 2012 02:14:40 +0200 [thread overview]
Message-ID: <4F837B70.2020307@opendreambox.org> (raw)
In-Reply-To: <cover.1334014014.git.mark.hatle@windriver.com>
On 10.04.2012 01:31, Mark Hatle wrote:
> The following is in reference to the recent discussion about the mips32
> -package- arch changing from mips to mips32. One of the potential options
> was to get rid of the previous "mips" and replace it with the mips32
> definition standard. This patch does just that.
>
> Working with Khem, we have moved the default "mips" (32-bit) tune to be
> -march=mips32 based, and produce package with the package arch of "mips".
>
> The side effect of this work is that the prior 'mips' tune was actually
> "mips1". I don't believe that was really desired by anyone, but it is a
> change. Also there is no longer a "mips32" tune, just an include file
> that automatically inherits and chooses the "mips" tune.
There's no backwards compatibility, but I'm fine with the new options.
The "mips" tune already gets selected by default in arch-mips.inc, so
you can remove it from tune-mips32.inc. Actually I'd prefer removing
tune-mips32.inc completely, so people will notice the
backwards-incompatible change.
Regards,
Andreas
next prev parent reply other threads:[~2012-04-10 0:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 23:31 [PATCH 0/1] MIPS/MIPS32 tune -> MIPS Mark Hatle
2012-04-09 23:31 ` [PATCH 1/1] tune-mips32: Update the default MIPS tuning to be mips32 Mark Hatle
2012-04-10 12:35 ` Phil Blundell
2012-04-10 12:37 ` Phil Blundell
2012-04-10 0:14 ` Andreas Oberritter [this message]
2012-04-10 0:20 ` [PATCH 0/1] MIPS/MIPS32 tune -> MIPS Mark Hatle
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=4F837B70.2020307@opendreambox.org \
--to=obi@opendreambox.org \
--cc=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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