glib crashes on start leaving you with a black screen and mouse pointer, cannot use ctrl-alt-Fn or ctrl-alt-del. This happens when compiling with -O3. I realise this is an upstream problem, but a rev of the ebuild with a filter/replace on -O3 to -O2 would be sensible. Reproducible: Always Steps to Reproduce: 1. Set -O3 in make.conf CFLAGS 2. emerge -1 glib 3. /etc/init.d/xdm start (with gdm selected in /etc/conf.d/xdm) Actual Results: Blank screen with mouse pointer, unresponsive system. May be able to login with ssh and kill, but occasionally crashes system requiring reset. Expected Results: gdm login screen appears with dialog, and able to use. I understand optimisation problems should be referred upstream, but as this causes a hang, it would seem sensible to replace the CFLAGS -O3 with -O2 until -O3 is working with glib again. -O3 is useful on core2/nehalem CPUs as it enables auto-vectorisation, which with the faster SSE units on core2 can make a big speed difference by using parallel SSE instructions. As per package CFLAGS are not supported, filtering the -O3 useflag on packages that are broken by optimisation would seem the only option, other than slowing down all packages (video encoding, scientific, etc...).
For now I consider this as a duplicate of bug #282341. We will not hide gcc bugs at -O3 level since we clearly state that gentoo gnome team nor upstream support optimization levels above -O2 [1]. Re-assigning to toolchain so they can ask you the appropriate informations if needs be. [1] http://www.gentoo.org/proj/en/desktop/gnome/gnome-policy.xml
Okay I have created the following file: /etc/portage/env/dev-libs/glib with the contents: CFLAGS=$(echo $CFLAGS | sed -e 's/-O3/-O2/g') Which gets my system working again. Posting here so other people can get their systems working.
(In reply to comment #1) > For now I consider this as a duplicate of bug #282341. We will not hide gcc > bugs at -O3 level since we clearly state that gentoo gnome team nor upstream > support optimization levels above -O2 [1]. Re-assigning to toolchain so they > can ask you the appropriate informations if needs be. > > [1] http://www.gentoo.org/proj/en/desktop/gnome/gnome-policy.xml > I have read the policy: Upstream GNOME does not support any advanced CFLAGS beyond -O2, and neither does the Gnome Herd. Unreproducable bugs with any CFLAGS beyond -O2 and appropriate -march are liable to be closed as INVALID unless they can be reproduced with valid CFLAGS. If this is the case, you really should replace the -O3 flag in the ebuild with -O2. To not do this leaves users with unusable systems (which is a Critical bug). They could have usable systems today if you filter -O3. Nowhere in the policy does it refer to hiding gcc bugs. So adding a filter for -O3 would be in compliance with the policy and would help users have working machines.
*** Bug 294387 has been marked as a duplicate of this bug. ***
(In reply to comment #1) > For now I consider this as a duplicate of bug #282341. We will not hide gcc > bugs at -O3 level since we clearly state that gentoo gnome team nor upstream > support optimization levels above -O2 [1]. Re-assigning to toolchain so they > can ask you the appropriate informations if needs be. > > [1] http://www.gentoo.org/proj/en/desktop/gnome/gnome-policy.xml > And to be more precise you can read at [2]: "Using -O3 is not recommended for gcc 4.x" 2. http://www.gentoo.org/doc/en/gcc-optimization.xml
(In reply to comment #5) > (In reply to comment #1) > > For now I consider this as a duplicate of bug #282341. We will not hide gcc > > bugs at -O3 level since we clearly state that gentoo gnome team nor upstream > > support optimization levels above -O2 [1]. Re-assigning to toolchain so they > > can ask you the appropriate informations if needs be. > > > > [1] http://www.gentoo.org/proj/en/desktop/gnome/gnome-policy.xml > > > > And to be more precise you can read at [2]: "Using -O3 is not recommended for > gcc 4.x" > > 2. http://www.gentoo.org/doc/en/gcc-optimization.xml > So why not filter it out? Other packages work fine with -O3, which has important optimisations for using SSE auto-vectorisation on the Core2 chips. If you do not want to support -O3, filter it out (swap -O3, for -O2). I can see no good reason for not filtering this flag in the ebuild. Infact based on your statement and the information provided, this flag should be filtered for all Gnome ebuilds.
Installed versions: 2.22.4(2)(05:23:11 PM 02/03/2010)(fam -debug -doc -hardened -selinux -xattr)
Is this still valid with updated systems?
