From: Mark Knecht <markknecht@gmail.com>
To: Xavier Miller <xavier.miller@cauwe.org>
Cc: John Kacur <jkacur@redhat.com>, RT <linux-rt-users@vger.kernel.org>
Subject: Re: Best gcc flags?
Date: Sat, 23 Jan 2010 14:27:34 -0800 [thread overview]
Message-ID: <5bdc1c8b1001231427k26a030ep4c15ceb918201849@mail.gmail.com> (raw)
In-Reply-To: <4B5B57F6.3050304@cauwe.org>
On Sat, Jan 23, 2010 at 12:11 PM, Xavier Miller <xavier.miller@cauwe.org> wrote:
> Hello,
>
> Don't play with CFLAGS/LDFLAGS. -march=native will let GCC find the best
> (and most sable) options for your compiler.
> Playing with unsafe CFLAGS/LDFLAGS will produce unstable system, hard to
> debug.
>
> Kind regards,
> Xavier Miller.
>
thanks. That's the direction I went. Trying to bring up X now. When
it's up I'll start working on adding rt-sources.
Cheers,
Mark
next prev parent reply other threads:[~2010-01-23 22:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 18:54 Best gcc flags? Mark Knecht
2010-01-22 22:09 ` John Kacur
2010-01-22 22:58 ` Mark Knecht
2010-01-23 20:11 ` Xavier Miller
2010-01-23 22:27 ` Mark Knecht [this message]
2010-01-24 13:45 ` Xavier Miller
2010-01-24 15:36 ` Mark Knecht
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=5bdc1c8b1001231427k26a030ep4c15ceb918201849@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=xavier.miller@cauwe.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;
as well as URLs for NNTP newsgroup(s).