After the mass rebuild, upgraded 32bit laptop to all packages. All text in gnome-terminal suddenly became black with red background. Huh? gnome-terminal-2.25.91-2.fc11.i586 vte-0.19.4-4.fc11.i586
Recompiling with replacing "-O2" with "-O0" seems to work for me, so I guess this is related to gcc optimization.
And also this affects Terminal in XFCE.
After some bisecting with #pragma optimize "O0", I found that adding __attribute__((optimize (0))) to _vte_terminal_insert_char is enough to fix vte.
that function is in src/vte.c
I see the same mess with x86_64.
My guess is a mis-optimization of the structure copies of defaults.attr, going to do a few builds and compare with 4.3 to test.
Can you please retry with __attribute__((noinline)) instead of optimize (0) on that function to make sure the problem is really in that function and not in the callers?
On x86_64 going back to vte-0.19.4-3.fc11.x86_64 doesn't help. Also, ncursesw gets colors very wrong on gnome-terminal.
(In reply to comment #8) > On x86_64 going back to vte-0.19.4-3.fc11.x86_64 doesn't help. > > Also, ncursesw gets colors very wrong on gnome-terminal. That's odd. I'm on x86_64 and reverting to 0.19.4-3.fc11 worked fine for me.
When reverting to older vte's, make sure to run: gnome-terminal --disable-factory (or pkill -f gnome-terminal) to make sure new terminal windows aren't just a new instance from the old gnome-terminal process (with the old vte loaded).
Jakub, with __attribute__((noinline)) it is still broken.
Apparently SRA messes things up, temporary workaround -fno-tree-sra.
(In reply to comment #9) > (In reply to comment #8) > > On x86_64 going back to vte-0.19.4-3.fc11.x86_64 doesn't help. > > > > Also, ncursesw gets colors very wrong on gnome-terminal. > That's odd. I'm on x86_64 and reverting to 0.19.4-3.fc11 worked fine for me. Right. After rebooting with the old vte it does work. Sorry.
I've built 0.19.4-5.f11 with a workaround now.
*** Bug 488104 has been marked as a duplicate of this bug. ***
gnome-terminal-2.25.91-2.fc11.i586 WFM Thanks for a quick response.
Should be fixed in gcc-4.4.0-0.22.