See http://gcc.gnu.org/PR53239 It would be nice not to have this wrong-code bug in F17 GA, internal compiler errors etc. are less severe than silent miscompilations. https://admin.fedoraproject.org/updates/FEDORA-2012-7449/gcc-4.7.0-5.fc17,gcc-python-plugin-0.9-4.fc17 fixes this bug.
Additionally, gcc-python-plugin will not install in current F17 tree, as it hasn't been rebuilt against any recent gcc.
I think this is meant to be proposed as NTH, not blocker. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
+1 NTH, I can see people doinga f17 install, and never updating it then wondering whats wrong with gcc.
-1 NTH this can be fixed with an update and it's impact on live images is going to be pretty small. (As far as I can tell gcc-python-plugin shouldn't end up on the install or live images; if it does and there is a problem installing that version, then I think this would be a blocker.)
-1 NTH as this could be fixed with an update and AFAIK, isn't on the DVD so users would have to hit the network to install this anyways.
Tim: gcc is on the DVD. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
(In reply to comment #6) > Tim: gcc is on the DVD. Yes, I know that but I thought this was an issue with gcc-python-plugin which, as far as I know, isn't on the DVD. If this is indeed an issue with the base gcc and not just gcc-python[23]-plugin, then I am less -1 NTH on this I don't pretend to completely understand the upstream bug but what are the possible side effects?
There is a gcc-c++ bug (well, several, this one is just most severe), where e.g. (for complete testcase look up the upstream bug): M test (M *x) { M n (R (0, 0)); for (int i = 0; i < 2; i++) { M p = x[i]; n = min (n, p); } return n; } from the testcase is miscompiled, can affect most of the C++ code (because named return value optimization is very common in C++). Here because M is not a POD type, the value is returned to memory pointed by a hidden argument, and NRV optimizes the code to have the variable n constructed in that memory. What the bug is about is that the value range propagation pass computed badly the expected range of the hidden argument (assumed it is uninitialized), and if you are unlucky enough like lilypond was, it can result in silent miscompilation of it. The gcc bug only affects gcc-* packages. The second issue is just that gcc-python-plugin, which depends on gcc exact NVR, hasn't been rebuilt for quite a while, so it has broken dependencies.
Discussed in the 2012-05-18 blocker bug review meeting. Accepted as NTH for Fedora 17 final because this could cause problems with c++ compilation with the gcc packages released on DVDs.
The update is pushed stable, so closing. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers