public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ryan Hill <dirtyepic.sk@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: [RFC] CFLAGS paragraph for the GWN
Date: Sat, 30 Sep 2006 16:37:05 -0600	[thread overview]
Message-ID: <efmrae$jff$1@sea.gmane.org> (raw)
In-Reply-To: <20060930215242.GK26289@curie-int.orbis-terrarum.net>

[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]

Robin H. Johnson wrote:
> On Sat, Sep 30, 2006 at 03:48:53PM -0600, Ryan Hill wrote:
>> Lionel Bouton wrote:
>>> There are already good resources (http://gentoo-wiki.com/CFLAGS_matrix
>>> was mentioned to me by robbat2) but they may not be advertised enough.
>> Most of the info on that page is wrong.
> The items on there that note breakages are reasonably correct.
> -fvisibility=hidden and -ffast-math DO cause breakages.
> 
> -ftree-loop-linear likewise is broken on GCC4.1 last I checked.

I thought he wanted flags that broke upgrading between GCC 3.4 and 4.1.
 tree-loop-linear wasn't in 3.4.  If you want flags that just break
stuff with 4.1 you can include -ftree-vectorize.

>>> I'd like to propose a paragraph to the GWN editor which presents some
>>> gotchas and good references on the subject.
>> Honestly, the only good reference is the Safe CFLAGS page.
> The objective here was mainly to point out some things that users are
> doing that are causing breakages, leading to bugs that are ultimately
> marked INVALID after much tracing.

Like using CFLAGS not on the Safe CFLAGS page?  ;)


Monsieur Spanky wrote:
> no way will our documentation link to gentoo-wiki.com

It's not documentation, it's the GWN, which has linked to gentoo-wiki
before.


--de.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-09-30 22:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-30 20:35 [gentoo-dev] [RFC] CFLAGS paragraph for the GWN Lionel Bouton
2006-09-30 20:58 ` Dominique Michel
2006-09-30 21:48 ` Mike Frysinger
2006-09-30 22:42   ` Lionel Bouton
2006-09-30 23:27     ` [gentoo-dev] " Ryan Hill
2006-09-30 21:48 ` Ryan Hill
2006-09-30 21:52   ` Robin H. Johnson
2006-09-30 22:37     ` Ryan Hill [this message]
2006-10-01  0:38       ` Robin H. Johnson
2006-10-01 11:23       ` Duncan
2006-10-01 16:49         ` Donnie Berkholz
2006-10-01 17:02           ` Diego 'Flameeyes' Pettenò
2006-10-01 18:00         ` Ryan Hill
2006-10-02 10:40           ` Duncan
2006-10-01 21:01         ` Jeroen Roovers
2006-10-01  0:37 ` [gentoo-dev] " George Prowse

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='efmrae$jff$1@sea.gmane.org' \
    --to=dirtyepic.sk@gmail.com \
    --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