[PATCH 4 of 7] cc/gcc: Add support for getting a gcc snapshot

Arnaud Lacombe lacombar@gmail.com
Tue Dec 14 05:04:00 GMT 2010


Hi,

On Fri, Dec 10, 2010 at 6:13 PM, Bryan Hundven <bryanhundven@gmail.com> wrote:
> On Fri, Dec 10, 2010 at 2:10 PM, Yann E. MORIN
> <yann.morin.1998@anciens.enib.fr> wrote:
>> Bryan, All,
>>
>> On Friday 10 December 2010 19:41:31 Bryan Hundven wrote:
>>> for _path in "LIST OF PATHS"; do
>>> for _file in $(find ${_path} -type f | xargs file | grep 'not
>>> stripped' | cut -d: -f1); do ${CT_TARGET}-strip ${_file}; done
>>> done
>>
>> Well, the question was rather about how to establish this "LIST OF PATHS"
>> in the first place. Once we have that, it's fairly easy to find executables
>> (and also libraries?) to be stripped.
>
> config STRIP_ALL_TOOLCHAIN_EXECUTABLES
>    bool
>    prompt "Strip all toolchain executables"
>    default y
>    help
>      All build host executables contain a lot of unnecessary info.
>      By stripping all executables it slightly speeds up the compilation
>      of large projects.
>      NOTE: It does NOT strip the target libraries, only HOST executables
>
>
> Right... I shouldn't be stripping libraries, unless we introduce
> STRIP_ALL_TOOLCHAIN_LIBRARIES... which we currently do not.
>
> Maybe this will suffice?:
>
>            for _file in $(find ${CT_PREFIX_DIR} -type f | xargs file | \
>                    grep 'not stripped'| grep 'executable' | cut -d: -f1); do
>                CT_DoExecLog ALL ${CT_HOST}-strip ${strip_args} "${_file}"
>            done
>
This will certainly not be needed on upcoming GCC 4.6, see
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46202 and
http://www.sourceware.org/ml/binutils/2010-10/msg00377.html. If you
feel like to backport these patch :)

  - Arnaud

--
For unsubscribe information see http://sourceware.org/lists.html#faq



More information about the crossgcc mailing list