From mboxrd@z Thu Jan 1 00:00:00 1970 From: Albert ARIBAUD Date: Thu, 2 Jul 2015 00:04:27 +0200 Subject: [U-Boot] [PATCH] ARM: enable CONFIG_USE_PRIVATE_LIBGCC by default (re-send to the correct address) In-Reply-To: <20150701215017.6E0DB38100A@gemini.denx.de> References: <1423571865-8579-1-git-send-email-yamada.m@jp.panasonic.com> <20150416112144.3a6b4813@lilith> <20150701234229.705fe4ce@lilith> <20150701215017.6E0DB38100A@gemini.denx.de> Message-ID: <20150702000427.562195b4@lilith> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hello Wolfgang, On Wed, 01 Jul 2015 23:50:17 +0200, Wolfgang Denk wrote: > Actually I think it is inherently wrong to enable > CONFIG_USE_PRIVATE_LIBGCC by default. > > This option is intended as a workaround for broken toolchains, until > these get fixed. By enabling this by default, we miss do not notice > the problems our tool chain has, and therefore these never get fixed, > i. e. brokenness grows. This cannot be good. > > CONFIG_USE_PRIVATE_LIBGCC should only be an emergency-opt-in, but > never ever a default setting. Well then, should we not revisit commits c3dd823 and 7bfd5ee, which enable CONFIG_USE_PRIVATE_LIBGCC for sh and mips respectively? Either we allow it by default for all architectures, or we forbid it by default for all architectures, but I don't like the idea of a heterogeneous per-arch default setting. > Best regards, > > Wolfgang Denk Amicalement, -- Albert.