Hi Richard:
thanks you comment :)
I send new patch for move -fno-builtin to common.opt and check it in
lto-lang.c (lto_post_options).
https://gcc.gnu.org/ml/gcc-patches/2014-08/msg02555.html
https://gcc.gnu.org/ml/gcc-patches/2014-08/msg02556.html
On Thu, Aug 28, 2014 at 5:29 PM, Richard Biener
On Thu, 28 Aug 2014, Kito Cheng wrote:
> Hi Richard:
>
> I think preserve -fno-builtin is better than
> -fno-tree-loop-distribute-patterns too,
>
> However if we preserve -fno-builtin, the coming problem is should we
> preserve all -fbuiltin-* and do the check logic[1] in common code in
> gcc?
Hi Richard:
I think preserve -fno-builtin is better than
-fno-tree-loop-distribute-patterns too,
However if we preserve -fno-builtin, the coming problem is should we
preserve all -fbuiltin-* and do the check logic[1] in common code in
gcc?
btw, in our internal gcc 4.9.x tree is move -fno-builtin
On Wed, Aug 27, 2014 at 4:42 PM, Kito Cheng wrote:
> Hi all:
>
> This patch basically is extension for r210100[1], stream out
> non-explicit -fno-tree-loop-distribute-patterns since compile with
> `-flto -O3 -fno-builtin` still may gen builtin function call during
> LTO phase.
>
> LTO bootstrapped
/viewcvs/gcc?view=revision&revision=210100
From a4d8d1218975413eba8a339e72066ef63649b8a6 Mon Sep 17 00:00:00 2001
From: Kito Cheng
Date: Tue, 26 Aug 2014 16:44:06 +0800
Subject: [PATCH] Steam out non-explicit -fno-tree-loop-distribute-patterns for
LTO options
2014-09-26 Kito Cheng
* lto-op
