Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Repetitive entries in Analyzer reports #99

Open
jenetscaria-mcw opened this issue Nov 11, 2024 · 10 comments
Open

Repetitive entries in Analyzer reports #99

jenetscaria-mcw opened this issue Nov 11, 2024 · 10 comments

Comments

@jenetscaria-mcw
Copy link

I have build my project with clang 19.1.3 version and ran the ClangBuildAnalyzer for the same and I am observing repetitive entries for compiler frontend. Is there a reason for it to show repetition in object files.
image

@jenetscaria-mcw jenetscaria-mcw changed the title Repitive entries for Repetitive entries in Analyzer reports Nov 11, 2024
@aras-p
Copy link
Owner

aras-p commented Nov 25, 2024

Hard to know why that would be happening, without knowing more details.

Are you building for multiple architectures by chance (e.g. Apple "Universal" binaries for both arm64 and x64)?

@jenetscaria-mcw
Copy link
Author

jenetscaria-mcw commented Dec 10, 2024

Hi @aras-p, thank you for the reply. We have build clang from source but only for one target without any cross compilation, i.e. Clang target = x86 in windows x64 machine.

I am attaching a spreadsheet where we have extracted the total frontend and backend timings along with the compiler frontend and backend files from our ClangBuildAnalyzer report for your reference. The repetitive entries are highlighted with blue.
ClangBuildAnalyzer_llama_report

@aras-p
Copy link
Owner

aras-p commented Dec 10, 2024

@jenetscaria-mcw I can't access the linked google sheet, permissions/sharing issue?

@jenetscaria-mcw
Copy link
Author

ClangBuildAnalyzer_llama_report.xlsx
@aras-p , sorry forgot about the access, here's the excel file for the same

@aras-p
Copy link
Owner

aras-p commented Dec 10, 2024

Ok but that still does not help in any way to know why it happened. The way ClangBuildAnalyzer works, is it tries to find all .json files under the build directory, checks which ones look like they are output by clang -ftime-trace, and aggregates info from them. So to understand why there are duplicates, I'd need a gather of all .json files under the directory that you use ClangBuildAnalyzer on.

@jenetscaria-mcw
Copy link
Author

output_all_json_files.zip
Here is a zip of all the json files generated under my build directory for your reference.

@aras-p
Copy link
Owner

aras-p commented Dec 10, 2024

@jenetscaria-mcw is that with the folder structure intact? I can see there are e.g. 16 files named get-model.cpp.json, but inside the zip file they all are under "root folder", and so they can't be properly unpacked.

My wild guess at this point would be that either you have some symbolic links under your build folder that point to the same folder several times, or that somehow under your build folder you ended up with json files from multiple builds, and now ClangBuildAnalyzer analyzes all of them.

@jenetscaria-mcw
Copy link
Author

output_json_files.zip
@aras-p, This will be the zip with all json files in the exact sub directories, there are multiple json files with the names but all correspond to different examples.

@aras-p
Copy link
Owner

aras-p commented Dec 10, 2024

@jenetscaria-mcw running ClangBuildAnalyzer on these json files does not result in any duplicate entries, as far as I can tell.

@jenetscaria-mcw
Copy link
Author

x86_102_report_1.txt
I am getting duplicate entries still. Attaching a result file generated from ClangBuildAnalyzer for your reference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants