| View previous topic :: View next topic |
| Author |
Message |
wrc1944
Advocate
Joined: 15 Aug 2002
Posts: 3435
Location: Gainesville, Florida
|
 Posted: Mon May 04, 2009 3:49 pm Post subject: |
 |
|
Noticed this in the ppl .config.log: | Quote: | gcc version 4.4.1-pre9999 built 20090503 (prerelease) rev. 147085 (Gentoo SVN)
configure:3309: $? = 0
configure:3316: i686-pc-linux-gnu-gcc -V >&5
i686-pc-linux-gnu-gcc: '-V' option must have argument
configure:3320: $? = 1
configure:3343: checking for C compiler default output file name
configure:3365: i686-pc-linux-gnu-gcc -O2 -march=k8 -pipe -fomit-frame-pointer -fno-ident -frename-registers -ftree-vectorize -floop-interchange -floop-strip-mine -floop-block -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed conftest.c >&5
conftest.c:1: sorry, unimplemented: Graphite loop optimizations cannot be used
configure:3369: $? = 1
configure:3407: result:
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME "the Parma Polyhedra Library"
| #define PACKAGE_TARNAME "ppl"
| #define PACKAGE_VERSION "0.10.2" |
After my emerge -e world is done without ppl/graphite, I'll try emerging ppl without --as-needed, and if that doesn't work, then disabling- ftree-vectorize and -fno-ident.
BTW, these flags have worked on all my Gentoo ~x86 systems for years with every version of gcc since 4.1.x, including 4.3.3.
Also, I added the Graphite flags (-floop-interchange -floop-strip-mine -floop-block) as recommended in this thread, but I got the "Graphite loop optimizations cannot be used" mentioned in the config.log file. Is adding these flags no longer correct, or now incorrect for the svn version?
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.8.4 USE=experimental python3_11 |
|
| Back to top |
|
 |
justinkb
Apprentice
Joined: 23 Dec 2008
Posts: 161
|
| Posted: Mon May 04, 2009 4:02 pm Post subject: |
|
|
| wrc1944 wrote: | | Hmm. ppl does have the -prolog USE flag, but I don't have swi-prolog even installed? Is that the problem? |
hm,, then my theory was incorrect. -prolog means you built it without prolog support, which wouldn't pull in anything else... let me think about it  |
|
| Back to top |
|
|
robnotts
Guru
Joined: 15 Mar 2004
Posts: 405
Location: Nottingham, UK
|
| Posted: Mon May 04, 2009 5:08 pm Post subject: |
|
|
| robnotts wrote: |
still have these problems...
dev-java/jaxme-0.3.1-r4
sci-libs/cln-1.2.2
dev-libs/boost-1.35.0-r2
dev-java/rhino-1.5.5-r4
media-gfx/exiv2-0.17
net-libs/xulrunner-1.8.1.19
dev-java/gnu-classpath-0.97-r1
x11-libs/qtscriptgenerator-0.1.0
media-tv/mythtv-0.22_alpha20308
kde-base/libkleo-4.2.2
kde-base/kleopatra-4.2.2
(x86 laptop, not the amd64 one as that one I do need to be stable!) |
Minor update, rhino-1.5.5-r4 wasn't actually needed, so has been unmerged. Upgrading to exiv2-0.18 allows that to compile, so that has been done. Boost has been solved by using the latest versions in the gcc-porting overlay...
7 packages to go for a completely gcc-4.4.0 compiled system, and I think looking at the mythtv dev site that they have applied fixes to mythtv to allow that to compile under gcc-4.4.0. Will report back later!
_________________
---
Gentoo Phenom][ X4 955 on AMD790 + Geforce 220GT 8GB/1.75TB (Desktop)
+ MythTV (3xFreeview,1xFreesat HD) on 1080p
Gentoo Turion64 X2 Geforce 6150 2GB/120GB (Laptop) |
|
| Back to top |
|
|
wrc1944
Advocate
Joined: 15 Aug 2002
Posts: 3435
Location: Gainesville, Florida
|
| Posted: Mon May 04, 2009 5:34 pm Post subject: |
|
|
@justinkb,
I think you misunderstood- my problem seems to be that I can't compile ppl yet, so I haven't built it with prolog, or without.
My emerge -e world is almost done- when it's through I'll try modifying LDFLAGS and/or CFLAGS. Hopefully, that will fix it up.
Hmm. Just thought- maybe the apparently default -prolog for ppl is incorrect now- maybe I should try ppl with prolog, and if that works see if I can then enable Graphite and get cloop-ppl and gcc with graphite, then do another emerge -e world with graphite.
I currently have 100 more world packages to go- only failure so far without graphite enabled (and ppl installed) is this non-essential package (for me, as this is mainly a kde-svn box): | Code: | >>> Preparing source in /var/tmp/portage/app-text/gnome-doc-utils-0.16.1/work/gnome-doc-utils-0.16.1 ...
* Fixing OMF Makefiles ... [ ok ]
* Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is:
*
* /usr/portage/app-text/gnome-doc-utils/files/gnome-doc-utils-0.16.0-fhs.patch
* ( gnome-doc-utils-0.16.0-fhs.patch )
*
* ERROR: app-text/gnome-doc-utils-0.16.1 failed. |
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.8.4 USE=experimental python3_11 |
|
| Back to top |
|
|
wrc1944
Advocate
Joined: 15 Aug 2002
Posts: 3435
Location: Gainesville, Florida
|
| Posted: Mon May 04, 2009 10:00 pm Post subject: |
|
|
OK- After my emerge -e world completed OK (just that one failure mentioned above).
Afterwards, I finally got ppl and cloog-ppl to compile. It wasn't a problem with my normal sets of cflags or ldflags.
I enabled the graphite USE flag in make.conf, but I had to remove the new cflags recommended here on this thread (-floop-interchange -floop-strip-mine -floop-block), then all went well.
I reread the thread, and maybe I just missed a correction or some comment about this, but is it actually still required required to have these new cflags in order to really enable Graphite in the new gcc? I've been reading other stuff on the net saying they are definitely required to actually enable graphite features. That seems to imply that without those cflags in make.conf, gcc won't actually have graphite enabled, even if you do have the graphite USE flag enabled.
Is the correct procedure to re-enable them in make.conf AFTER compiling ppl and cloog-ppl without them, and then recompile gcc with them (and graphite USE flag), and then do another emerge -e world? During this emerge -e world, won't ppl/cloog-ppl again fail when they come up, as the new cflags will again be in make.conf?
Or, do they not now need to be in make.conf at all, and the graphite USE flag (and ebuild instructions) now cover everything adding the flags used to, and gcc will indeed have the graphite features even without the cflags?
On my system, I definitely cannot compile ppl/cloog-ppl with them enabled, but can't compile gcc (but only with the graphite USE flag enabled) without ppl/cloog-ppl installed.
If anyone is successfully compiling ppl and cloog-ppl WITH these cflags in make.conf, please post back, as that will indicate I have something else wrong here.
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.8.4 USE=experimental python3_11 |
|
| Back to top |
|
|
justinkb
Apprentice
Joined: 23 Dec 2008
Posts: 161
|
| Posted: Mon May 04, 2009 10:08 pm Post subject: |
|
|
the compiler flags only work when gcc has been compiled with graphite support.
1) emerge gcc with graphite use flag without those cflags set
2) change to new gcc compiler
3) enable the flags if you want them
4) go crazy with emerge -e world or whatever you want |
|
| Back to top |
|
|
wrc1944
Advocate
Joined: 15 Aug 2002
Posts: 3435
Location: Gainesville, Florida
|
| Posted: Mon May 04, 2009 10:12 pm Post subject: |
|
|
Thanks justinkb,
Will do.
UPDATE: OK- Just finished up a complere emerge -e world (605 packages), with only the gnome-doc-utils failure (missing epatch?)- no big deal for me.  Now have a Gentoo system compiled with gcc-4.4.1_pre9999, graphite features enabled. (During the compile, the new cflags were showing up in the gcc output). Still need to dd a complete kde-svn update on this box.
Many thanks to all for the tips and feedback! 
To summarize, on my x~86 kde-svn install box, I had to do the following in this specific order.
1. emerge --sync portage and overlays, then emerge -uD @system and emerge -uD @world.
2. Install gcc-4.4.1_pre9999, WITHOUT graphite USE flag and WITHOUT the three new cflags in make.conf.
3. Switch to new compiler, and rebuild the complete toolchain.
4. emerge -e @system && emerge -e @world
5. Install ppl and cloog-ppl, still WITHOUT graphite USE flag and WITHOUT the three new cflags in make.conf. If these flags are in make.conf, ppl and cloog-ppl fail, at least on my system. Both ppl and cloog-ppl are required for compiling gcc with graphite USE flag enabled.
6. Enable graphite USE FLAG in make.conf, and then emerge gcc-4.4.1_pre9999 again.
7. Add -floop-interchange -floop-strip-mine -floop-block to cflags make.conf, and then once again do emerge -e world.
My relevant make.conf flags that worked on this system are:
| Quote: | CFLAGS="-O2 -march=k8 -pipe -fomit-frame-pointer -fno-ident -frename-registers -ftree-vectorize -floop-interchange -floop-strip-mine -floop-block"
CXXFLAGS="${CFLAGS}"
LDFLAGS="-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed"
CHOST="i686-pc-linux-gnu"
ACCEPT_KEYWORDS="~x86"
USE="graphite -ipv6 -bluetooth -fam X opengl kdeprefix 3dnow 3dnowext 3dnowprefetch mmx mmxext smp -apache -apache2 -gnome gtk2 sse sse2 glibc-omitfp" |
The march=k8 is because I'm on amd64 hardware, but the Gentoo install is 32bit for this partition. I will in the near future try gcc.4.4.1_pre9999 on my other pure 64bit Gentoo installation partition, same hardware.
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.8.4 USE=experimental python3_11 |
|
| Back to top |
|
|
Basso Buffo
n00b
Joined: 19 Oct 2007
Posts: 24
Location: North Carolina, USA
|
| Posted: Tue May 05, 2009 6:51 pm Post subject: |
|
|
wrc1944, I think you are making things too difficult for yourself. The reason you couldn't compile ppl and cloog-ppl with the -floop-* flags is that GCC only recognizes these flags if you have *already* compiled it with cloog/graphite support. So first, you have to build ppl and cloog-ppl before you add graphite to your USE flags. Four steps:
| Code: | CFLAGS="-O2 -march=k8 -pipe -fomit-frame-pointer" emerge -1 ppl cloog-ppl
CFLAGS="-O2 -march=k8 -pipe -fomit-frame-pointer" USE="graphite" emerge =sys-devel/gcc-4.4.1-pre9999
gcc-config select x86-pc-linux-gnu-4.4.1-pre9999
CFLAGS="-O2 -march=k8 -pipe -fomit-frame-pointer -floop-interchange -floop-strip-mine -floop-block" emerge -e @world |
|
|
| Back to top |
|
|
kernelOfTruth
Watchman
Joined: 20 Dec 2005
Posts: 6111
Location: Vienna, Austria; Germany; hello world :)
|
| Posted: Tue May 05, 2009 9:22 pm Post subject: |
|
|
| Basso Buffo wrote: | wrc1944, I think you are making things too difficult for yourself. The reason you couldn't compile ppl and cloog-ppl with the -floop-* flags is that GCC only recognizes these flags if you have *already* compiled it with cloog/graphite support. So first, you have to build ppl and cloog-ppl before you add graphite to your USE flags. Four steps:
| Code: | CFLAGS="-O2 -march=k8 -pipe -fomit-frame-pointer" emerge -1 ppl cloog-ppl
CFLAGS="-O2 -march=k8 -pipe -fomit-frame-pointer" USE="graphite" emerge =sys-devel/gcc-4.4.1-pre9999
gcc-config select x86-pc-linux-gnu-4.4.1-pre9999
CFLAGS="-O2 -march=k8 -pipe -fomit-frame-pointer -floop-interchange -floop-strip-mine -floop-block" emerge -e @world |
|
++
think of it like the following:
1) I'm explaining you steps for building a computer in a foreign language
you can't understand it (cloog, ppl missing)
2) you learn parts of that foreign language where needed or get yourself a nice dictionary
(emerging cloog, ppl with the old compiler)
3) you are able to understand the before mentioned instructions (emerge gcc with USE="graphite")
4) now you can build the computer (re-emerging world with those -floop flags activated)
_________________
https://github.com/kernelOfTruth/ZFS-for-SystemRescueCD/tree/ZFS-for-SysRescCD-4.9.0
https://github.com/kernelOfTruth/pulseaudio-equalizer-ladspa
Hardcore Gentoo Linux user since 2004 |
|
| Back to top |
|
|
loftwyr
l33t
Joined: 29 Dec 2004
Posts: 970
Location: 43°38'23.62"N 79°27'8.60"W
|
| Posted: Tue May 05, 2009 9:26 pm Post subject: |
|
|
Can anyone give me an idea of the benefits of the graphite system? I've read the docs but don't really know if there's a specific benefit to using the flags globally.
_________________
My emerge --info
Have you run revdep-rebuild lately? It's in gentoolkit and it's worth a shot if things don't work well.
Celebrating 5 years of Gentoo-ing. |
|
| Back to top |
|
|
wrc1944
Advocate
Joined: 15 Aug 2002
Posts: 3435
Location: Gainesville, Florida
|
| Posted: Wed May 06, 2009 12:30 pm Post subject: |
|
|
Thanks guys- I really appreciate you taking the time to give detailed replies!
Basso Buffo wrote: | Quote: | | wrc1944, I think you are making things too difficult for yourself. |
Of course you're right, but that's been the case for the last 65 years! 
I eventually arrived at essentially the 4 step solution you posted, as I outlined in the post right above yours. Yours was certainly expressed more succinctly. 
kernelOfTruth wrote:
| Quote: | 2) you learn parts of that foreign language where needed or get yourself a nice dictionary
(emerging cloog, ppl with the old compiler) |
True, however at the time I wasn't using the old compiler (4.3.3), but using the new one.
I am experiencing problems with kde-svn (3 failures on emerge @kdebase-live) with the gcc-4.4.1_pre9999 partition. If interested, please see my 2 posts on Page 32 of the kde-testing thread, towards the end, for details https://forums.gentoo.org/viewtopic-t-722264-start-775.html?sid=74f2c5dfc1fc3c5888c9b46de23e662b
In order to see if the kde-svn problem is indeed gcc-4.4.1_pree9999 related, I'm currently doing a complete kde-svn rebuild on another identical Gentoo install (same box, different partition), however this one is 64 bit, and is still using portage gcc-4.3.3. Thought it was a qt version problem, but now I'm not so sure, as I've tried both qt portage and qting-edge, and get same failures. 
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.8.4 USE=experimental python3_11 |
|
| Back to top |
|
|
gringo
Advocate
Joined: 27 Apr 2003
Posts: 3793
|
| Posted: Wed May 06, 2009 3:56 pm Post subject: |
|
|
| Quote: | | Can anyone give me an idea of the benefits of the graphite system? I've read the docs but don't really know if there's a specific benefit to using the flags globally. |
i was actually going to ask the same because i don´t see any benefits either ...
cu
_________________
Error: Failing not supported by current locale |
|
| Back to top |
|
|
wrc1944
Advocate
Joined: 15 Aug 2002
Posts: 3435
Location: Gainesville, Florida
|
| Posted: Wed May 06, 2009 5:23 pm Post subject: |
|
|
OK- I installed the qting-edge qt-copy on an identical Gentoo install gcc-4.3.3, kde-svn, pure 64 bit box. | Code: | amd64 portage # emerge -pv1 @qt-all-live-kde
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild U ] x11-libs/qt-core-4.5.9999 [4.5.1] USE="glib iconv qt-copy%* qt3support ssl -debug -doc -pch (-custom-cxxflags%)" 0 kB [0=>1]
[ebuild U ] x11-libs/qt-sql-4.5.9999 [4.5.1] USE="iconv mysql qt-copy%* qt3support sqlite -debug (-firebird) -odbc -pch -postgres (-custom-cxxflags%)" 0 kB [0=>1]
[ebuild U ] x11-libs/qt-script-4.5.9999 [4.5.1] USE="iconv qt-copy%* -debug -pch (-custom-cxxflags%)" 0 kB [0=>1]
[ebuild U ] x11-libs/qt-dbus-4.5.9999 [4.5.1] USE="qt-copy%* -debug -pch (-custom-cxxflags%)" 0 kB [0=>1]
[ebuild U ] x11-libs/qt-test-4.5.9999 [4.5.1] USE="iconv qt-copy%* -debug -pch (-custom-cxxflags%)" 0 kB [0=>1]
[ebuild U ] x11-libs/qt-xmlpatterns-4.5.9999 [4.5.1] USE="qt-copy%* -debug -pch (-custom-cxxflags%)" 0 kB [0=>1]
[ebuild U ] x11-libs/qt-gui-4.5.9999 [4.5.1] USE="accessibility cups dbus glib gtkstyle qt-copy%* qt3support -debug -mng -nas -nis -pch -raster -tiff -xinerama (-custom-cxxflags%)" 0 kB [0=>1]
[ebuild U ] x11-libs/qt-qt3support-4.5.9999 [4.5.1] USE="accessibility qt-copy%* -debug -pch -phonon (-custom-cxxflags%)" 0 kB [0=>1]
[ebuild U ] x11-libs/qt-webkit-4.5.9999 [4.5.1] USE="qt-copy%* -debug -pch (-custom-cxxflags%)" 0 kB [0=>1]
[ebuild U ] x11-libs/qt-svg-4.5.9999 [4.5.1-r1] USE="iconv qt-copy%* -debug -pch (-custom-cxxflags%)" 0 kB [0=>1]
[ebuild U ] x11-libs/qt-opengl-4.5.9999 [4.5.1] USE="qt-copy%* qt3support -debug -pch (-custom-cxxflags%)" 0 kB [0=>1]
[ebuild U ] x11-libs/qt-assistant-4.5.9999 [4.5.0_rc1] USE="qt-copy%* -debug -pch (-custom-cxxflags%)" 0 kB [1]
Total: 12 packages (12 upgrades), Size of downloads: 0 kB
Portage tree and overlays:
[0] /usr/portage
[1] /usr/local/portage/layman/qting-edge
|
I got the same errors as before, so it appears it has nothing to do with 32 or 64 bit, or gcc-4.3.3 or gcc-4.4.1_pre9999.
On each system, I get this: | Code: | >>> Preparing source in /var/tmp/portage/kde-base/plasma-workspace-9999-r1/work/plasma-workspace-9999 ...
* Injecting library dependencies from 'libkworkspace libplasmaclock libtaskmanager' ... [ ok ]
* Enabling experimental fake transparency support.
* There are known issues with certain versions of Qt.
* Do not report any bugs.
* Applying plasma-workspace-fake-panel-transparency.patch ...emerge -1pv @kdeartwork-live @kdeadmin-live @kdepim-live kde-base/gwenview ark kdf okular marble dragonplayer kde-misc/konq-plugins kde-misc/webkit-kpart
* Failed Patch: plasma-workspace-fake-panel-transparency.patch !
* ( /usr/local/portage/layman/kde-testing/kde-base/plasma-workspace/files/plasma-workspace-fake-panel-transparency.patch )
*
* Include in your bugreport the contents of:
*
* /var/tmp/portage/kde-base/plasma-workspace-9999-r1/temp/plasma-workspace-fake-panel-transparency.patch-27604.out
* emerge -1pv @kdeartwork-live @kdeadmin-live @kdepim-live kde-base/gwenview ark kdf okular marble dragonplayer kde-misc/konq-plugins kde-misc/webkit-kpart
* ERROR: kde-base/plasma-workspace-9999-r1 failed.
* Call stack:
* ebuild.sh, line 49: Called src_prepare
* environment, line 4085: Called epatch '/usr/local/portage/layman/kde-testing/kde-base/plasma-workspace/files/plasma-workspace-fake-panel-transparency.patch'
* environment, line 1986: Called die
* The specific snippet of code:
* die "Failed Patch: ${patchname}!";
* The die message:
* Failed Patch: plasma-workspace-fake-panel-transparency.patch! |
Yesterday, I tried commenting out the fake-panel-transparency patch in the ebuild, and re-digested, but it still failed. At least I know pretty much know it's not gcc-4.4.1 related, and must be a qt version problem, like the message says.
Can someone who has compiled kdebase-live recently please clue me in as to WHICH qt version from qting-edge is the right one, if any? I have also tried portage qr-4.5.1, and get the same error.
The message "There are known issues with certain versions of Qt" doesn't help much- why don't they just tell you which versions cause problems? Essentially, my kde-svn boxes are now broken, as plasma-workspace is a vital package. 
UPDATE: OK- this time commenting out the fake-panel-transparency and redigesting the ebuild worked. Don't know if it was that, or all the updates plasma-workspace just got. This was on the pure amd64 64bit install with gcc-4.3.3-r1, and qt-all-live-kde from qting-edge. I'll try the gcc-4.4.1_pre9999 box tomorrow.
UPDATE2: Finished up on my gcc-4.4.1_pre9999 box with kde-svn, using qt-all-live-kde from qting-edge.
Again, as with the gcc-4.3.3 box, I had to comment out the fake-panel-transparency patch and redigest the ebuild.
However, set @kdepim-live fails because libkdepim (first package) fails- | Code: | | Could NOT find KdepimLibs (missing: KdepimLibs_CONFIG) |
Haven't found a workaround. On the bright side, all my other kde-svn selected packages are working, and report version:
| Quote: | Dolphin
Version 1.2.80
Using KDE 4.2.85 (KDE 4.2.85 (KDE 4.3 Beta1)) |
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.8.4 USE=experimental python3_11 |
|
| Back to top |
|
|
Judge584
Tux's lil' helper
Joined: 18 Apr 2005
Posts: 109
|
| Posted: Thu May 07, 2009 10:11 am Post subject: |
|
|
| Gcc 4.4 is now in Portage (Hard Masked). |
|
| Back to top |
|
|
cruzki123
Apprentice
Joined: 16 May 2008
Posts: 262
|
| Posted: Thu May 07, 2009 10:28 am Post subject: |
|
|
| gringo wrote: | | Quote: | | Can anyone give me an idea of the benefits of the graphite system? I've read the docs but don't really know if there's a specific benefit to using the flags globally. |
i was actually going to ask the same because i don´t see any benefits either ...
cu |
If you had programed VERY carefully your programs, expecialy that with a lot of nested bucles with heavy math computations inside, you don't obtaind almost any gain. But, if you didn't, now the compiler can optimace this nested bucles acording to the computer, perhaps maken less computations, perhaps making it more parallel code, perhaps making more cache friendly, etc.
I suppose the real impact will be en some mathematicaly intensive aplication as ffmpeg, etc but this one have been already optimized (with asm code) so rpobabily you cannot gain very much |
|
| Back to top |
|
|
Basso Buffo
n00b
Joined: 19 Oct 2007
Posts: 24
Location: North Carolina, USA
|
| Posted: Thu May 07, 2009 6:31 pm Post subject: |
|
|
| Having built everything on my box with GCC 4.4, I've noticed that Inkscape is now crashing on startup. Is anyone else seeing this? I suspect that the problem may be solved by applying the patch found at https://bugs.launchpad.net/inkscape/+bug/337357, but I won't be able to tell until I get home tonight. If it fixes the problem, I'll submit a Gentoo bug. |
|
| Back to top |
|
|
kernelOfTruth
Watchman
Joined: 20 Dec 2005
Posts: 6111
Location: Vienna, Austria; Germany; hello world :)
|
|
| Back to top |
|
|
Basso Buffo
n00b
Joined: 19 Oct 2007
Posts: 24
Location: North Carolina, USA
|
| Posted: Thu May 07, 2009 7:06 pm Post subject: |
|
|
I doubt it. I'm not using nVidia's proprietary drivers, and I don't recall seeing a specific FPE error.
That does give me an idea, though. The problem has only cropped up recently -- and I recently switched over to using the nouveau driver. Coincidence? I'm not so sure. Tonight I'll switch over to nv and see if the problem persists. Or maybe I'll go back to nvidia-drivers. Or it's entirely possible that the SVN patch I linked to earlier takes care of the issue, since it was reported to fix a crash-on-start bug. |
|
| Back to top |
|
|
kernelOfTruth
Watchman
Joined: 20 Dec 2005
Posts: 6111
Location: Vienna, Austria; Germany; hello world :)
|
|
| Back to top |
|
|
Basso Buffo
n00b
Joined: 19 Oct 2007
Posts: 24
Location: North Carolina, USA
|
| Posted: Fri May 08, 2009 2:20 am Post subject: |
|
|
| OK, I just submitted the Inkscape bug, and about 10 minutes later it was RESOLVED FIXED, along with about 5 other bugs that are blocking the GCC 4.4 tracker bug. It looks like they are moving things through quickly now that 4.4 is in the tree. |
|
| Back to top |
|
|
ComaWhite
Tux's lil' helper
Joined: 07 Oct 2008
Posts: 125
|
| Posted: Sat May 09, 2009 8:19 am Post subject: |
|
|
| hopefully stabled in a couple of months |
|
| Back to top |
|
|
Neo2
Apprentice
Joined: 25 Sep 2006
Posts: 224
Location: Italy
|
| Posted: Mon May 11, 2009 2:46 pm Post subject: |
|
|
| loftwyr wrote: | | Can anyone give me an idea of the benefits of the graphite system? I've read the docs but don't really know if there's a specific benefit to using the flags globally. |
You can read of the changes here: GCC 4.4 changes.
Graphite optimizations allow some transformations on loops that improve cache locality and decrease code size, mainly by "splitting" larger loops and making them iterate over smaller amounts of data; this allows both loop code and loop data to fit into the CPU's caches, avoiding to refetch data from the memory. All of this should lead to faster execution for heavily loop-based programs (eg: video processing/maths calculations). In a usual system there should be just few programs that are so loop-dependant. Obviously also common programs benefit of these optimizations, but since the common program doesn't spend that much time iterating over 3-dimensional [1024x1024x1024] arrays, the visible gain should be near to nonexistent.
The biggest global performance gain should come from IRA (Integrated Register Allocator) which kills the old register allocator; it uses more modern/efficient algorithms for register allocation and has better integration with the usual optimization passes. This should result in visible (yet theoretically little) performance gains.
Also, a new instruction scheduler and software pipeliner has been added, which should provide global nearly-visible benefits. Quoting the changes:
| Quote: | | A new instruction scheduler and software pipeliner, based on the selective scheduling approach, has been added. The new pass performs instruction unification, register renaming, substitution through register copies, and speculation during scheduling. The software pipeliner is able to pipeline non-countable loops. The new pass is targeted at scheduling-eager in-order platforms. In GCC 4.4 it is available for the Intel Itanium platform working by default as the second scheduling pass (after register allocation) at the -O3 optimization level. |
that translated in human terms should say: "when there's a CPU that spends a lot of time scheduling the code to execute, we can make its life easier" (I guess mainly computational/server systems).
Hope to have clarified the situation a little.
Cheers,
Neo2
_________________
Neo2
Unofficial minimal liveCD for x86/amd64 w/reiser4+truecrypt |
|
| Back to top |
|
|
dhallas
n00b
Joined: 22 Sep 2004
Posts: 22
Location: Denmark
|
| Posted: Mon May 11, 2009 7:01 pm Post subject: |
|
|
I have upgraded my system to gcc 4.4.0 and everything compiled fine, but vim keeps crashing with a ABRT signal. I tried updating glibc to the latest masked version in portage (sys-libs/glibc-2.9_p20081201-r2) but that didn't fix the problem. I have added "-ggdb" to my cflags and "splitdebug" to features and recompiled everything, and then ran vim under gdb, that gave the following backtrace:
| Code: |
#0 0xb7f73e41 in *__GI__dl_debug_state () at dl-debug.c:76
#1 0xb7f687cb in dl_main (phdr=0x1, phnum=3086501464, user_entry=0xb7f73e40) at rtld.c:2334
#2 0xb7f79a83 in _dl_sysdep_start (start_argptr=0xbfc83ae0, dl_main=0xb7f674a0 <dl_main>) at ../elf/dl-sysdep.c:239
#3 0xb7f66361 in _dl_start (arg=<value optimized out>) at rtld.c:330
#4 0xb7f659a7 in _start () from /lib/ld-linux.so.2
|
This is my emerge --info
| Code: |
Portage 2.1.6.11 (default/linux/x86/2008.0, gcc-4.4.0, glibc-2.9_p20081201-r2, 2.6.28-gentoo-r5 i686)
=================================================================
System uname: Linux-2.6.28-gentoo-r5-i686-Intel-R-_Pentium-R-_4_CPU_3.20GHz-with-glibc2.0
Timestamp of tree: Mon, 11 May 2009 03:15:01 +0000
ccache version 2.4 [disabled]
app-shells/bash: 3.2_p39
dev-lang/python: 2.5.4-r2
dev-util/ccache: 2.4-r7
sys-apps/baselayout: 1.12.11.1
sys-apps/sandbox: 1.6-r2
sys-devel/autoconf: 2.63
sys-devel/automake: 1.10.2
sys-devel/binutils: 2.18-r3
sys-devel/gcc-config: 1.4.0-r4
sys-devel/libtool: 1.5.26
virtual/os-headers: 2.6.27-r2
ACCEPT_KEYWORDS="x86"
ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci"
ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol"
APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias"
ARCH="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=native -pipe -ggdb"
CHOST="i686-pc-linux-gnu"
CLEAN_DELAY="5"
COLLISION_IGNORE="/lib/modules"
CONFIG_PROTECT="/etc"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/gconf /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/udev/rules.d"
CVS_RSH="ssh"
CXXFLAGS="-O2 -march=native -pipe -ggdb"
DISTDIR="/tmp/portage/distfiles"
EDITOR="/bin/nano"
ELIBC="glibc"
EMERGE_DEFAULT_OPTS="--ask --verbose"
EMERGE_WARNING_DELAY="10"
FEATURES="distlocks fixpackages parallel-fetch protect-owned sandbox sfperms splitdebug strict unmerge-orphans userfetch"
FETCHCOMMAND="/usr/bin/wget -t 5 -T 60 --passive-ftp -O "${DISTDIR}/${FILE}" "${URI}""
GCC_SPECS=""
GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo"
HOME="/root"
INFOPATH="/usr/share/info:/usr/share/binutils-data/i686-pc-linux-gnu/2.18/info:/usr/share/gcc-data/i486-pc-linux-gnu/4.1.2/info:/usr/share/gcc-data/i686-pc-linux-gnu/4.4.0/info"
INPUT_DEVICES="keyboard mouse evdev"
KERNEL="linux"
LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text"
LDFLAGS="-Wl,-O1"
LESS="-R -M --shift 5"
LESSOPEN="|lesspipe.sh %s"
LINGUAS="en da"
LOGNAME="root"
LS_COLORS="rs=0:di=01;34:ln=01;36:hl=44;37:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.rar=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01;35:*.ogx=01;35:*.pdf=00;32:*.ps=00;32:*.txt=00;32:*.patch=00;32:*.diff=00;32:*.log=00;32:*.tex=00;32:*.doc=00;32:*.aac=00;36:*.au=00;36:*.flac=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.axa=00;36:*.oga=00;36:*.spx=00;36:*.xspf=00;36:"
MANPATH="/usr/local/share/man:/usr/share/man:/usr/share/binutils-data/i686-pc-linux-gnu/2.18/man:/usr/share/gcc-data/i486-pc-linux-gnu/4.1.2/man:/usr/share/gcc-data/i686-pc-linux-gnu/4.4.0/man"
NETBEANS="apisupport cnd groovy gsf harness ide identity j2ee java mobility nb php profiler soa visualweb webcommon websvccommon xml"
PAGER="/usr/bin/less"
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/i486-pc-linux-gnu/gcc-bin/4.1.2:/usr/i686-pc-linux-gnu/gcc-bin/4.4.0"
PKGDIR="/usr/portage/packages"
PORTAGE_ARCHLIST="ppc s390 amd64 x86 ppc64 x86-fbsd m68k arm sparc sh mips ia64 alpha hppa amd64-fbsd sparc-fbsd"
PORTAGE_BINHOST_CHUNKSIZE="3000"
PORTAGE_BIN_PATH="/usr/lib/portage/bin"
PORTAGE_COMPRESS_EXCLUDE_SUFFIXES="css gif htm[l]? jp[e]?g js pdf png"
PORTAGE_CONFIGROOT="/"
PORTAGE_DEBUG="0"
PORTAGE_DEPCACHEDIR="/var/cache/edb/dep"
PORTAGE_ELOG_CLASSES="log warn error"
PORTAGE_ELOG_MAILFROM="portage@localhost"
PORTAGE_ELOG_MAILSUBJECT="[portage] ebuild log for ${PACKAGE} on ${HOST}"
PORTAGE_ELOG_MAILURI="root"
PORTAGE_ELOG_SYSTEM="save_summary echo"
PORTAGE_FETCH_CHECKSUM_TRY_MIRRORS="5"
PORTAGE_FETCH_RESUME_MIN_SIZE="350K"
PORTAGE_GID="250"
PORTAGE_INST_GID="0"
PORTAGE_INST_UID="0"
PORTAGE_PYM_PATH="/usr/lib/portage/pym"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_RSYNC_RETRIES="3"
PORTAGE_TMPDIR="/var/tmp"
PORTAGE_VERBOSE="1"
PORTAGE_WORKDIR_MODE="0700"
PORTDIR="/usr/portage"
PROFILE_ONLY_VARIABLES="ARCH ELIBC KERNEL USERLAND"
PWD="/root"
RESUMECOMMAND="/usr/bin/wget -c -t 5 -T 60 --passive-ftp -O "${DISTDIR}/${FILE}" "${URI}""
ROOT="/"
ROOTPATH="/opt/bin:/usr/i486-pc-linux-gnu/gcc-bin/4.1.2:/usr/i686-pc-linux-gnu/gcc-bin/4.4.0"
RPMDIR="/usr/portage/rpm"
SHELL="/bin/bash"
SHLVL="1"
SYNC="rsync://alpha/gentoo-portage"
TERM="xterm"
USE="acl berkdb bzip2 cli cracklib crypt cups dri fortran gdbm gpm iconv ipv6 isdnlog midi mudflap ncurses nls nptl nptlonly openmp pam pcre perl pppd python readline reflection session spl ssl sysfs tcpd unicode x86 xorg zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en da" USERLAND="GNU" VIDEO_CARDS="fbdev glint i810 intel mach64 mga neomagic nv r128 radeon savage sis tdfx trident vesa vga via vmware voodoo"
USER="root"
USERLAND="GNU"
USE_EXPAND="ALSA_CARDS ALSA_PCM_PLUGINS APACHE2_MODULES APACHE2_MPMS CAMERAS CROSSCOMPILE_OPTS DVB_CARDS ELIBC FCDSL_CARDS FOO2ZJS_DEVICES FRITZCAPI_CARDS INPUT_DEVICES KERNEL LCD_DEVICES LINGUAS LIRC_DEVICES MISDN_CARDS NETBEANS_MODULES USERLAND VIDEO_CARDS"
USE_EXPAND_HIDDEN="CROSSCOMPILE_OPTS ELIBC KERNEL USERLAND"
USE_ORDER="env:pkg:conf:defaults:pkginternal:env.d"
VIDEO_CARDS="fbdev glint i810 intel mach64 mga neomagic nv r128 radeon savage sis tdfx trident vesa vga via vmware voodoo"
_="/usr/bin/emerge"
|
Any ideas?
A little update, I ran vim under valgrind and got the following interesting output:
| Code: |
**27145** *** strcpy_chk: buffer overflow detected ***: program terminated
==27145== at 0x4029EDB: VALGRIND_PRINTF_BACKTRACE (valgrind.h:3695)
==27145== by 0x402A07E: __strcpy_chk (mc_replace_strmem.c:614)
==27145== by 0x809D59B: call_user_func (string3.h:106)
==27145== by 0x809E1E7: call_func (eval.c:8007)
==27145== by 0x809EC95: get_func_tv (eval.c:7854)
==27145== by 0x80A6997: ex_call (eval.c:3305)
==27145== by 0x80C3755: do_one_cmd (ex_docmd.c:2621)
==27145== by 0x80C19A3: do_cmdline (ex_docmd.c:1095)
==27145== by 0x80D3A3B: apply_autocmds_group (fileio.c:8790)
==27145== by 0x80F3880: main (main.c:810)
|
So this looks to be a vim bug, I will dig a bit further into this...
_________________
Cheers
David
Last edited by dhallas on Mon May 11, 2009 7:39 pm; edited 1 time in total |
|
| Back to top |
|
|
mv
Watchman
Joined: 20 Apr 2005
Posts: 6749
|
| Posted: Mon May 11, 2009 7:38 pm Post subject: |
|
|
| dhallas wrote: | | I have upgraded my system to gcc 4.4.0 and everything compiled fine, but vim keeps crashing with a ABRT signal. |
You need vim-7.2.108. Older versions had problems with FORTIFY_SOURCE=2. Of course, you can hack CFLAGS=-U_FORTIFY_SOURCE if you want to risk the buggy version. |
|
| Back to top |
|
|
dhallas
n00b
Joined: 22 Sep 2004
Posts: 22
Location: Denmark
|
| Posted: Mon May 11, 2009 7:48 pm Post subject: |
|
|
| mv wrote: | | dhallas wrote: | | I have upgraded my system to gcc 4.4.0 and everything compiled fine, but vim keeps crashing with a ABRT signal. |
You need vim-7.2.108. Older versions had problems with FORTIFY_SOURCE=2. Of course, you can hack CFLAGS=-U_FORTIFY_SOURCE if you want to risk the buggy version. |
Upgrading to vim-7.2.108 fixed the problem, maybe we should have a stabilization bug for vim-7.2.108 blocking the gcc-4.4.0 tracker? Should I create one?
_________________
Cheers
David |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Unsupported Software
