Displaying 5 results from an estimated 5 matches for "sbwriteresgroup2".
2018 Mar 17
2
[cfe-dev] Clang executable sizes and build stats
I'm sure the x86 scheduler models are causing bloat. Every time a single
instruction appears on a line by itself like this in a scheduler model:
def: InstRW<[SBWriteResGroup2], (instregex "ANDNPDrr")>;
It causes that instruction to be its own group in the generated output. And
its replicated for each CPU. We should look into better using regular
expressions or taking advantage of the fact that InstRW can take a list of
instructions. That makes those instru...
2018 Mar 21
0
[cfe-dev] Clang executable sizes and build stats
> On Mar 17, 2018, at 4:04 PM, Craig Topper via cfe-dev <cfe-dev at lists.llvm.org> wrote:
>
> I'm sure the x86 scheduler models are causing bloat. Every time a single instruction appears on a line by itself like this in a scheduler model:
>
> def: InstRW<[SBWriteResGroup2], (instregex "ANDNPDrr")>;
>
> It causes that instruction to be its own group in the generated output. And its replicated for each CPU. We should look into better using regular expressions or taking advantage of the fact that InstRW can take a list of instructions. That makes th...
2018 Mar 22
1
[cfe-dev] Clang executable sizes and build stats
...gt;
> On Mar 17, 2018, at 4:04 PM, Craig Topper via cfe-dev <
> cfe-dev at lists.llvm.org> wrote:
>
> I'm sure the x86 scheduler models are causing bloat. Every time a single
> instruction appears on a line by itself like this in a scheduler model:
>
> def: InstRW<[SBWriteResGroup2], (instregex "ANDNPDrr")>;
>
> It causes that instruction to be its own group in the generated output.
> And its replicated for each CPU. We should look into better using regular
> expressions or taking advantage of the fact that InstRW can take a list of
> instructions....
2018 Mar 17
0
[cfe-dev] Clang executable sizes and build stats
Thanks for raising this. This is something we've recently been looking at
too at Sony, as over the course of PS4's lifetime so far we've seen our
clang executable on Windows approximately double in size, which isn't ideal
for things like distributed build systems. A graph of clang.exe size on
our internal staging branch matches yours closely with it being more of a
death by a
2018 Mar 17
2
Clang executable sizes and build stats
Hi all,
I recently did a run where I built clang executables on FreeBSD 12-CURRENT [1], from trunk r250000 (2015-10-11) all through r327700 (2018-03-16), with increments of 100 revisions. This is mainly meant as an archive, for easily doing bisections, but there are also some interesting statistics.
From r250000 through r327700:
* the total (stripped) executable size grew by approximately 43%
*