From: Rafa Griman <rafagriman@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] revdep-rebuild (gawk) issues
Date: Tue, 29 May 2012 23:37:31 +0200 [thread overview]
Message-ID: <CANRt_=aON81uian-Ap2KA0b6PN8Ebk5=oaufPx88M+=qphsxYw@mail.gmail.com> (raw)
In-Reply-To: <20120529230937.13e48154@khamul.example.com>
On Tue, May 29, 2012 at 11:09 PM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> On Tue, 29 May 2012 22:56:07 +0200
> Rafa Griman <rafagriman@gmail.com> wrote:
>
>> Hi Vaeth :)
>>
>> On Tue, May 29, 2012 at 7:02 PM, Vaeth
>> <vaeth@mathematik.uni-wuerzburg.de> wrote:
>> > On Tue, 29 May 2012, Rafa Griman wrote:
>> >>
>> >> gawk: cmd. line:3: error: Unmatched [ or [^: /[^[:space:]]/
>> >
>> >
>> > Your gawk is broken. This happens if you emerged gawk with
>> > current gcc and aggressive FLAGS like -DNDEBUG or -flto.
>> > Not sure whether it is a bug of gawk or gcc.
>>
>>
>> So it seems to be the CFLAGS :( As I said in my previous e-mail, I was
>> "experimenting" a bit with them ... I'll be more conservative ;)
>
> Well, on the one hand the flags don;t seem to be too bad overall, but
> on the other hand there's the golden rule of Gentoo:
>
> Don't stuff around with CFLAGS
>
> Why not? Well, there's the ricer phenomenon where changed CFLAGS
> worsen performance and stability but the user's own bias convinces
> him/her that it's actually vastly improved.
I know that rule and tried not to be too agressive but seems I was O:)
Since it's not my min machine, I was going to experiment (nothing
"scientific", just curiosity) trying different options on different
partitions and see how they work out.
> Some tweaks are perfectly OK, like the multimedia and cpu-specific
> stuff (sse, mmx and all their related cousins). These are normally safe
> and can give huge gains with video playback. Likewise for the GPU tweaks
> once those hit mainline usage.
That was mainly the reason: video playback and some other apps
(scientific). But nothing serious.
> One last tweak, if the code is built on the machine that will run it
> (the usual case, replace -march and -mtune with just "-march=native".
> It has exactly the same effect but is easier to read, is
> self-documenting and allows the compiler to attempt it's best (the
> compiler usually does know much better what to do than you do)
I totally agree with you: the compiler knos better ;)
TIA
Rafa
next prev parent reply other threads:[~2012-05-29 21:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <j6uYa-sw-27@gated-at.bofh.it>
2012-05-29 17:02 ` [gentoo-user] revdep-rebuild (gawk) issues Vaeth
2012-05-29 20:56 ` Rafa Griman
2012-05-29 21:09 ` Alan McKinnon
2012-05-29 21:37 ` Rafa Griman [this message]
2012-05-30 18:37 ` Florian Philipp
2012-05-30 20:17 ` Rafa Griman
2012-05-29 13:34 Rafa Griman
2012-05-29 14:35 ` Alan McKinnon
2012-05-29 15:26 ` Rafa Griman
2012-05-29 20:49 ` Rafa Griman
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='CANRt_=aON81uian-Ap2KA0b6PN8Ebk5=oaufPx88M+=qphsxYw@mail.gmail.com' \
--to=rafagriman@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