From: Denis <denis.che@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] which -march flag to pick for Intel Core 2 Duo in make.conf?
Date: Thu, 24 May 2007 12:38:19 -0400 [thread overview]
Message-ID: <d9a0a6da0705240938y4bc79b28u28f85c037095e9a7@mail.gmail.com> (raw)
In-Reply-To: <20070524164310.46a03922@zaphod.digimed.co.uk>
On 5/24/07, Neil Bothwick <neil@digimed.co.uk> wrote:
> Bear in mind that GCC is almost certainly masked for good reason. It's
> not like you're using a binary distro and only need a compiler for a few
> packages. Feel free to try it in the knowledge that if it breaks your
> system, you get to keep the pieces.
Ain't it the truth! No, I wasn't asking with the anxiety to hurry
things up - I was asking more about an estimated release time, whether
it will be a month, 2 months, 3 months, etc.
I'm not really looking to "experiment" with the cutting-edge releases
right now. My aim is to build a fast, stable system for my
computations, which ultimately brought me to another major decision:
32-bit or 64-bit... I run simulations which I write in C and
numerical computations which I run in Mathematica (which has just
released the 64-bit version). Would a 64-bit system significantly
benefit these applications?
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-05-24 16:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 13:55 [gentoo-user] which -march flag to pick for Intel Core 2 Duo in make.conf? Denis
2007-05-24 14:15 ` Ryan Sims
2007-05-24 14:17 ` Mark Shields
2007-05-24 15:13 ` Denis
2007-05-24 15:43 ` Neil Bothwick
2007-05-24 15:55 ` Graham Murray
2007-05-24 16:38 ` Denis [this message]
2007-05-25 7:22 ` Randy Barlow
2007-05-24 15:30 ` [gentoo-user] " Alexander Skwar
-- strict thread matches above, loose matches on Subject: below --
2007-05-25 9:10 [gentoo-user] " burlingk
2007-05-25 17:03 ` Andreas Claesson
2007-05-25 18:26 ` Denis
2007-05-28 3:05 ` Randy Barlow
2007-05-31 1:11 ` Dan Farrell
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=d9a0a6da0705240938y4bc79b28u28f85c037095e9a7@mail.gmail.com \
--to=denis.che@gmail.com \
--cc=gentoo-user@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