Change Details

This option is for groups who need time to accomodate the ld.lld -z nostart-stop-gc default. This is off by default because we have evidence that very few groups need the behavior. There are anecdotal or non-anecdotal evidences that many groups are fine with the -z nostart-stop-gc default (matching GNU ld<2015-10): Android, Chrome OS (Linux), Fuchsia, Google, Meta, SN systems, some Gentoo Linux users I asked using -fuse-ld=lld (with or without using Clang). -z nostart-stop-gc default matches ld64 behavior for `section\$start` symbols and encourages in-tree and out-tree developers to think about section based linker garbage collection prudently.

This option is for groups who need time to accomodate the ld.lld -z nostart-stop-gc default. This is off by default because we have evidence that very few groups need the behavior. There are anecdotal or non-anecdotal evidences that many groups are fine with the -z nostart-stop-gc default (matching GNU ld<2015-10): Android, Chrome OS (Linux), Fuchsia, Google, Meta, SN systems, some Gentoo Linux users I asked using -fuse-ld=lld (with or without using Clang). -z nostart-stop-gc default matches ld64 behavior for `section$start` symbols and encourages in-tree and out-tree developers to think about section based linker garbage collection prudently.

This option is for groups who need time to accomodate the ld.lld -z nostart-stop-gc default. This is off by default because we have evidence that very few groups need the behavior. There are anecdotal or non-anecdotal evidences that many groups are fine with the -z nostart-stop-gc default (matching GNU ld<2015-10): Android, Chrome OS (Linux), Fuchsia, Google, Meta, SN systems, some Gentoo Linux users I asked using -fuse-ld=lld (with or without using Clang). -z nostart-stop-gc default matches ld64 behavior for `section\$start` symbols and encourages in-tree and out-tree developers to think about section based linker garbage collection prudently.