If renderer.lib is built with enough debug flags, it will exceed 2 GB on Windows |
||
Issue descriptionWhat steps will reproduce the problem? (1) Turn on a lot of debug flags (2) Turn on link time code generation (3) Build 32 bit renderer.lib What is the expected result? A renderer.lib What happens instead? An unhappy linker complaining that renderer.lib is too large (more than 2GB)
,
Jan 17 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/99eedf26ca7066208384f7c46ca8dfd23242c2d4 commit 99eedf26ca7066208384f7c46ca8dfd23242c2d4 Author: bratell <bratell@opera.com> Date: Tue Jan 17 21:14:32 2017 Split renderer.lib on Windows to avoid files larger than 2GB. In certain configurations renderer.lib can exceed 2GB in size which is too much for the 32 bit build tools. Splitting it avoids that problem. BUG= 679644 Review-Url: https://codereview.chromium.org/2622583005 Cr-Commit-Position: refs/heads/master@{#444143} [modify] https://crrev.com/99eedf26ca7066208384f7c46ca8dfd23242c2d4/content/renderer/BUILD.gn
,
Jan 17 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by brat...@opera.com
, Jan 10 2017