Summary: | ICE in struct initializer when taking address | ||
---|---|---|---|
Product: | gcc | Reporter: | Jim White <jwhite> |
Component: | middle-end | Assignee: | Not yet assigned to anyone <unassigned> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gcc-bugs, NitinY |
Priority: | P2 | Keywords: | ice-on-valid-code |
Version: | 3.3 | ||
Target Milestone: | 3.3.2 | ||
Host: | Target: | ||
Build: | Known to work: | ||
Known to fail: | Last reconfirmed: | 2003-09-08 02:17:51 |
Description
Jim White
2003-07-24 21:31:17 UTC
I can confirm gcc ICEs on this in 2.95.3, 3.0.4, 3.2.2, 3.2.3, 3.3.1 (20030707) and the mainline (20030724) so this is not a regression. Dunno whether the code is valid or not. C language experts? This is valid c as the initializer does not have to be a constant when it in a function. Also this ICE on the C++ front-end too, so this is a middle-end problem, most likely related to bug 11852 (might even was fixed by it, I did not test GCC with the patch). I will tentatively put the target as 3.3.2 and I will retest it when I bootstrap with updated sources with the patch already applied. Guess what it is fixed by the same patch which fixed bug 11852 so commiting a testcase for this one. Forgot to say this is fixed in 3.3.2 and 3.4. |