public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Samuli Suominen <ssuominen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Adding --as-needed to LDFLAGS in profiles/default/linux/make.defaults
Date: Mon, 28 Jun 2010 11:08:22 +0300	[thread overview]
Message-ID: <4C285876.4020208@gentoo.org> (raw)
In-Reply-To: <20100628085119.1631337d@snowcone>

On 06/28/2010 10:51 AM, Ciaran McCreesh wrote:
> On Mon, 28 Jun 2010 10:44:54 +0300
> Samuli Suominen <ssuominen@gentoo.org> wrote:
>>> You've forgotten "make --as-needed not break correct code by making
>>> the linker ignore explicit instructions from a program author to
>>> link two things together". Until you do that, --as-needed is in the
>>> same category as -ffast-math.
>>
>> And we can't be held hostage by few packages (marginal cases), that's
>> why we have function called $(no-as-needed) in flag-o-matic.eclass to
>> disable the behavior for these packages.
> 
> Will Gentoo be doing the same for -Ofast and its flags then? After all,
> most packages work with them, and you can't let the few packages that
> require standard-compliant behaviour from a compiler hold Gentoo
> hostage.
> 

This is not about optimizing but preventing clear breakage, the benefits
of asneeded are not under debate here (like already stated in the
original message this thread started from)

So please stop trying to derail the thread

- Samuli



  parent reply	other threads:[~2010-06-28  8:07 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-28  1:09 [gentoo-dev] Adding --as-needed to LDFLAGS in profiles/default/linux/make.defaults Nirbheek Chauhan
2010-06-28  7:23 ` [gentoo-dev] " Christian Faulhammer
2010-06-28  7:35 ` [gentoo-dev] " Ciaran McCreesh
2010-06-28  7:44   ` Samuli Suominen
2010-06-28  7:51     ` Ciaran McCreesh
2010-06-28  8:04       ` [gentoo-dev] " Nikos Chantziaras
2010-06-28  8:08       ` Samuli Suominen [this message]
2010-06-28  8:10         ` [gentoo-dev] " Nirbheek Chauhan
2010-06-28 13:43           ` Thomas Anderson
2010-06-28 13:59             ` Roy Bamford
2010-06-28 14:05               ` Ciaran McCreesh
2010-06-29  3:30                 ` Jeroen Roovers
2010-06-29  7:23                   ` Ciaran McCreesh
2010-06-29  8:46                     ` Alex Alexander
2010-06-29 17:25                       ` David Leverton
2010-06-29 17:59                         ` Alex Alexander
2010-07-05 13:01                 ` [gentoo-dev] " Peter Hjalmarsson
2010-07-05 13:47                   ` Arun Raghavan
2010-07-05 14:25                   ` David Leverton
2010-06-28  8:16         ` [gentoo-dev] " Ciaran McCreesh
2010-06-28 11:09           ` [gentoo-dev] " Duncan
2010-06-28 11:46             ` David Leverton
2010-06-28 15:21               ` Brian Harring
2010-06-29  6:27                 ` [gentoo-dev] [OT] h v l Mike Frysinger
2010-06-29  6:35                   ` Luis Araujo
2010-06-28  8:17 ` [gentoo-dev] Adding --as-needed to LDFLAGS in profiles/default/linux/make.defaults Markos Chandras
2010-06-28  9:21   ` Nirbheek Chauhan
2010-06-28  8:42 ` Pacho Ramos
2010-06-28 12:11 ` Alex Alexander
2010-06-29 17:04 ` David Leverton

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=4C285876.4020208@gentoo.org \
    --to=ssuominen@gentoo.org \
    --cc=gentoo-dev@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