Summary: | Spurious 'might be used uninitialized' warnings in STL headers with -O2 | ||
---|---|---|---|
Product: | gcc | Reporter: | brian |
Component: | middle-end | Assignee: | Not yet assigned to anyone <unassigned> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dave.korn.cygwin, gcc-bugs, ian, james, pdemarco |
Priority: | P2 | Keywords: | diagnostic |
Version: | 3.4.4 | ||
Target Milestone: | 4.0.0 | ||
Host: | Target: | i686-pc-cygwin | |
Build: | Known to work: | 4.1.0 | |
Known to fail: | 3.4.4 | Last reconfirmed: | 2005-09-06 18:59:23 |
Bug Depends on: | |||
Bug Blocks: | 24639 | ||
Attachments: | Preprocessed source for testcase |
Description
brian
2005-06-27 23:08:17 UTC
Created attachment 9163 [details]
Preprocessed source for testcase
Confirmed that this happens with 3.4 for the i686-pc-cygwin target, though not for the i686-pc-linux-gnu target. It is fixed in current mainline for both targets. Fixed in 4.0.0. any chance of getting this fixed on 3.4.4 ??? Sorry mate, all 3.x compilers are way past end-of-life now; there will never be another release. Your best bet is to hand-edit the header files in your local install. I don't remember the exact recipe, but of the two places where this bug crops up, one can be worked around by adding "__attribute__ ((__unused__))" to the relevant variable declaration, and the other one has to be fixed by adding "__attribute__ ((__noinline__))" to the function declaration. I haven't tested these workaround for performance impact. Shouldn't be too bad if you're not calling the functions from the middle of a loop that runs millions of times. (In reply to comment #5) > Sorry mate, all 3.x compilers are way past end-of-life now; there will never be > another release. okay, but I wish that you wouldn't freeze 3.x when 4.x is still in Alpha. If I could upgrade to a stable 4.x for the change... I would. (In reply to comment #6) > okay, but I wish that you wouldn't freeze 3.x when 4.x is still in Alpha. Alpha?!? What do you mean, exactly? Certainly we have a very stable 4.3.x release series, and previously we had 4.2.x, and previously 4.1.x... (In reply to comment #7) > (In reply to comment #6) > > okay, but I wish that you wouldn't freeze 3.x when 4.x is still in Alpha. > Alpha?!? What do you mean, exactly? Certainly we have a very stable 4.3.x > release series, and previously we had 4.2.x, and previously 4.1.x... My understanding was that 4.x was not available. I'll have to re-check. sorry for the noise. Subject: Re: Spurious 'might be used uninitialized' warnings in STL headers with -O2 You are confusing the state of the Cygwin port of gcc with gcc in general. (In reply to comment #9) > Subject: Re: Spurious 'might be used uninitialized' > warnings in STL headers with -O2 > You are confusing the state of the Cygwin port of gcc with gcc in > general. Possibly, but I cannot find the download for 4.x.x. Why does it have to be so confusing ? http://sourceforge.net/project/showfiles.php?group_id=2435 This is the location that I got ALPHA from. It appears that the best 4.x.x download is: Testing: gcc-4.3.0-20080502-mingw32-alpha I see no other reasonable downloads. Brian is right: http://gcc.gnu.org/mirrors.html |