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

L1Trigger/CSCTrackFinder: disable optimizer on Clang #7416

Conversation

davidlt
Copy link
Contributor

@davidlt davidlt commented Jan 28, 2015

Clang is causing issues (not only to CMS) with high memory usage in
some scenarios. vpp_* generates files require 12.5GB of RSS with Clang,
while only using 0.5GB with GCC. This was tested from Clang 3.3 to Clang
3.6 and trunk (2015 Jan 28).

This is reported upstream and few people already looking into it. Also
causes issue to KDE/QT people.

Also this causes machine building CMSSW with Clang to go offline in Jenkins.
The job continues to run on build machine, but Jenkins looses the state. Then
Jenkins assumes that machine is free and could launch another CMSSW build
job causing more stress on machine.

Tested with GCC and Clang. Bypassing.

Signed-off-by: David Abdurachmanov David.Abdurachmanov@cern.ch

Clang is causing issues (not only to CMS) with high memory usage in
some scenarios. vpp_* generates files require 12.5GB of RSS with Clang,
while only using 0.5GB with GCC. This was tested from Clang 3.3 to Clang
3.6 and trunk (2015 Jan 28).

This is reported upstream and few people already looking into it. Also
causes issue to KDE/QT people.

Signed-off-by: David Abdurachmanov <David.Abdurachmanov@cern.ch>
davidlt added a commit that referenced this pull request Jan 28, 2015
…er-CSCTrackFinder

L1Trigger/CSCTrackFinder: disable optimizer on Clang
@davidlt davidlt merged commit e7c6dfc into cms-sw:CMSSW_7_4_X Jan 28, 2015
@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

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

Successfully merging this pull request may close these issues.

None yet

2 participants