Bug 43776 - cpu hog with '-O1 -g2' / var-tracking issue?
Summary: cpu hog with '-O1 -g2' / var-tracking issue?
Status: RESOLVED DUPLICATE of bug 41371
Alias: None
Product: gcc
Classification: Unclassified
Component: debug (show other bugs)
Version: 4.5.0
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-17 09:11 UTC by Pawel Sikora
Modified: 2010-05-16 12:22 UTC (History)
8 users (show)

See Also:
Host: x86_64-gnu-linux
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed:


Attachments
testcase. (118.15 KB, application/octet-stream)
2010-04-17 09:11 UTC, Pawel Sikora
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Pawel Sikora 2010-04-17 09:11:19 UTC
here's a small testcase that shows cpu hog in 4.5.
for bigger files, the hog is much bigger :(

$ time g++43 1.ii -c -O1 -g2
g++43 1.ii -c -O1 -g2  11,25s user 0,20s system 99% cpu 11,474 total

$ time g++44 1.ii -c -O1 -g2
g++44 1.ii -c -O1 -g2  8,53s user 0,25s system 99% cpu 8,795 total

$ time g++45 1.ii -c -O1 -g2
1.ii: In member function 'void es::ClockAnalyzer::initPrimitives()':
1.ii:38722:7: note: variable tracking size limit exceeded with -fvar-tracking-assignments, retrying without
g++45 1.ii -c -O1 -g2  34,73s user 0,45s system 99% cpu 35,237 total
Comment 1 Pawel Sikora 2010-04-17 09:11:57 UTC
Created attachment 20406 [details]
testcase.
Comment 2 Richard Biener 2010-04-17 11:16:26 UTC
That's the usual KDE var-tracking issue.  Do we still have a PR open to mark
this as a dup of?
Comment 3 Pawel Sikora 2010-05-16 12:22:50 UTC

*** This bug has been marked as a duplicate of 41371 ***