On Fri, Jan 24, 2014 at 10:51 AM, Sean Farley <s...@macports.org> wrote:
>
> eg...@gwmail.gwu.edu writes:
>
>> Just so it can remove it with the `+debug` variant that it adds, it looks
>> like...
>
> Eric is correct. In hindsight, I am now doubting adding
> -mtune=native. Maybe just the -O3 -Ofast etc.?
>
>> On Thu, Jan 23, 2014 at 10:32 PM, Joshua Root <j...@macports.org> wrote:
>>
>>> On 2014-1-24 09:50 , Sean Farley wrote:
>>> >
>>> > lar...@macports.org writes:
>>> >
>>> >> (a) There's already a configure.mtune option. You should use that
>>> ("configure.mtune native") instead of appending to all the flags options.
>>> >
>>> > Oh, awesome, thanks for the tip.
>>> >
>>> >> (b) Don't you have to disable binary archives if you set
>>> "-mtune=native"?
>>> >
>>> > Probably so. Luckily, there are no ports using this port group so this
>>> > kind of feedback is appreciated.
>>>
>>> (c) Why is a portgroup called "debug" adding -mtune=native anyway?
>>>
>>> - Josh
>>> _______________________________________________
>>> macports-dev mailing list
>>> macports-dev@lists.macosforge.org
>>> https://lists.macosforge.org/mailman/listinfo/macports-dev
>>>
>
> _______________________________________________
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev-mtune=native also breaks gcc prior to 4.4(? Prior to some version. ;) ... and similar (llvm-gcc-4.2) I would take it out, not to mention that anything built with -mtune=native may not be the best choice for binary distribution. (Although it should be OK; -march=native would be a definite no-no.) - Eric _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
