public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: memset_s
Date: Wed, 15 Nov 2017 12:39:23 -0500	[thread overview]
Message-ID: <996c1436-ed56-6ad7-1c68-d4ebed42da1f@gentoo.org> (raw)
In-Reply-To: <CAKpSnpKnNG77_ESNLJHwOoHetvs_rXs31mPfvEcV52s=sYnRPA@mail.gmail.com>

On 11/15/2017 10:50 AM, Jorge Almeida wrote:
>
> Are you really sure? I was under the impression that ebuilds did it,
> and I find that natural. I didn't view that as a bug at all.


On principle, most things in the tree should respect whatever CFLAGS,
LDFLAGS, etc. you ask for. The problems resulting from that are
predictable: if you add "-ffast-math" to your CFLAGS and then start
getting crashes; well, you asked for it. We're not going to fix that for
you in every ebuild.

On the other hand, there are packages where some optimizations fail due
to a compiler bug or something else that is not by design. Some packages
optimize their critical path in assembly, and the resulting code doesn't
play well with otherwise-reasonable CFLAGS. In cases like those, it's
often simpler to disable the problematic flag in the ebuild rather than
have a thousand people do the same thing locally.


  reply	other threads:[~2017-11-15 17:39 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-10  9:54 [gentoo-user] memset_s Jorge Almeida
2017-11-10 10:52 ` Marc Joliet
2017-11-10 11:34   ` Jorge Almeida
2017-11-10 16:25     ` R0b0t1
2017-11-10 18:20       ` Alexander Kapshuk
2017-11-10 20:09       ` Jorge Almeida
2017-11-10 23:19         ` R0b0t1
2017-11-11  0:10           ` Jorge Almeida
2017-11-13  3:03             ` Mart Raudsepp
2017-11-13  7:17               ` Jorge Almeida
2017-11-13 10:44                 ` [gentoo-user] memset_s Nikos Chantziaras
2017-11-13 11:16                   ` Jorge Almeida
2017-11-13 11:38                   ` Mart Raudsepp
2017-11-13 14:26                     ` Nikos Chantziaras
2017-11-14 17:36         ` [gentoo-user] memset_s Jorge Almeida
2017-11-15  4:42           ` R0b0t1
2017-11-15  7:22             ` Jorge Almeida
2017-11-15 15:28             ` [gentoo-user] memset_s Grant Edwards
2017-11-15 15:41               ` R0b0t1
2017-11-15 15:48                 ` R0b0t1
2017-11-15 21:42                   ` Grant Edwards
2017-11-16  0:19                     ` R0b0t1
2017-11-15 15:50                 ` Jorge Almeida
2017-11-15 17:39                   ` Michael Orlitzky [this message]
2017-11-15  8:54           ` Nikos Chantziaras
2017-11-15  9:05             ` Jorge Almeida
2017-11-15 10:31               ` Nikos Chantziaras
2017-11-10 11:38 ` Nikos Chantziaras

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=996c1436-ed56-6ad7-1c68-d4ebed42da1f@gentoo.org \
    --to=mjo@gentoo.org \
    --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