From: Sebastian Pipping <sping@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] [rfc] simplifying arch classes
Date: Mon, 27 Jun 2011 19:41:49 +0200 [thread overview]
Message-ID: <4E08C0DD.5010003@gentoo.org> (raw)
In-Reply-To: <BANLkTikRAXECejd_6mmw_w3=7HCgGE-3NA@mail.gmail.com>
On 06/27/2011 07:15 AM, Matt Turner wrote:
> class arch_mips(generic):
> "MIPS class"
> def __init__(self, Olevel, arch, additional_cflags, include_workarounds):
> generic.__init__(self)
>
> self.settings["CFLAGS"] = "-O" + Olevel
> self.settings["CFLAGS"] += " -march=" + arch
> if additional_cflags != "":
> self.settings["CFLAGS"] += " " + additional_cflags
> if include_workarounds:
> if arch == "mips3":
> self.settings["CFLAGS"] += " -mfix-r4000 -mfix-r4400"
> elif arch == "r4000" or arch == "r4k":
> self.settings["CFLAGS"] += " -mfix-r4000"
> elif arch == "r4300":
> self.settings["CFLAGS"] += " -mfix-r4300"
> elif arch == "r10000" or arch == "r10k":
> self.settings["CFLAGS"] += " -mfix-r10000"
> self.settings["CFLAGS"] += " -pipe"
Thoughts:
- How are you going to ensure that such refactoring keeps all
~50 cases working without writing 50 explicit, data-duplicating
test cases? Would you be willing to write these?
- The code above adds flexibility but is less obvious than
the current code. So while it improves on one aspect
it worsens on another.
- Such refactoring would have to be done on both 2.x and 3.x branches.
Better wait until we are clear on their future.
Best,
Sebastian
next prev parent reply other threads:[~2011-06-27 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 5:15 [gentoo-catalyst] [rfc] simplifying arch classes Matt Turner
2011-06-27 17:41 ` Sebastian Pipping [this message]
2011-06-27 17:58 ` Matt Turner
2011-06-27 18:18 ` Sebastian Pipping
2011-06-27 18:24 ` Matt Turner
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=4E08C0DD.5010003@gentoo.org \
--to=sping@gentoo.org \
--cc=gentoo-catalyst@lists.gentoo.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