[llvm-bugs] [Bug 46050] New: Output files are fragmented
via llvm-bugs
llvm-bugs at lists.llvm.org
Sat May 23 06:39:19 PDT 2020
https://bugs.llvm.org/show_bug.cgi?id=46050
Bug ID: 46050
Summary: Output files are fragmented
Product: clang
Version: 10.0
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: unassignedclangbugs at nondot.org
Reporter: lev-sch at mail.ru
CC: htmldeveloper at gmail.com, llvm-bugs at lists.llvm.org,
neeilans at live.com, richard-llvm at metafoo.co.uk
Created attachment 23525
--> https://bugs.llvm.org/attachment.cgi?id=23525&action=edit
files to reproduce
Hello.
I've found that clang++.exe produces fragmented output files.
Average fragmentation is 3 fragments per file.
Please make output without fragmentation. It helps to get high compilation
speed.
Steps to reproduce on windows platform:
1. unpack attachment
2. fill configuration area in run.cmd
3. start run.cmd
4. wait for all clang processes are created and wait for they exit
5. use "getFileFragmentation.cmd path_to_out" command to get fragmentation info
for output folder. (getFileFragmentation.cmd can be added to
%APPDATA%\Microsoft\Windows\SendTo)
Solution described is here
https://sourceforge.net/p/sevenzip/feature-requests/981/
> D:\temp\clangFragmentation\out\f1.dep is in 4 fragments
> D:\temp\clangFragmentation\out\f1.o is in 2 fragments
> (...)
>
> Summary:
> Number of files processed: 48
> Number unsuccessfully procesed: 0
> Average fragmentation : 3 frags/file
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20200523/872d2510/attachment.html>
More information about the llvm-bugs
mailing list