Summary: | GCC doesn't duplicate computed gotos for functions marked as "hot" | ||
---|---|---|---|
Product: | gcc | Reporter: | Dmitry Stogov <dmitry> |
Component: | middle-end | Assignee: | Not yet assigned to anyone <unassigned> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dmitry, gcc-bugs, jaak, ktietz |
Priority: | P3 | Keywords: | missed-optimization |
Version: | 4.4.3 | ||
Target Milestone: | 5.0 | ||
Host: | i686-redhat-linux | Target: | i686-redhat-linux |
Build: | i686-redhat-linux | Known to work: | |
Known to fail: | Last reconfirmed: |
Description
Dmitry Stogov
2010-04-08 12:46:22 UTC
yes. It's definitely the same issue. The only additional note that __attribute__((hot)) doesn't fix the problem (as I would expect tracing down optimize_bb_for_size_p()), but makes an additional slowdown. In opposite, the __attribute__((cold)) solves the issue. It looks very strange. I suppose some condition has to be inverted :) (In reply to comment #1) > Duplicate of PR42621? And probably a duplicate of bug 39284 also. (In reply to comment #2) > yes. It's definitely the same issue. > > The only additional note that __attribute__((hot)) doesn't fix the problem (as > I would expect tracing down optimize_bb_for_size_p()), but makes an additional > slowdown. In opposite, the __attribute__((cold)) solves the issue. It looks > very strange. > > I suppose some condition has to be inverted :) Both __attribute__((cold)) and __attribute__((hot)) have this issue with GCC 4.5.2 on my Gentoo Linux box. Neither of them solves it. |