Subject: Re: filter_tomsmocomp && gcc4 - msg#00004

Previous Message by Date: click to view message preview

Re: filter_tomsmocomp && gcc4

On Jul 03, 05 14:39:52 -0700, Jacob Meuser wrote: > On Sun, Jul 03, 2005 at 12:29:10PM +0200, Erik Slagter wrote: > > On Sat, 2005-07-02 at 13:25 -0700, Jacob Meuser wrote: > > > the tomsmocomp filter doesn't build for me with > > > > > has anyone else seen this? I don't remember seeing a report about > > > tomsmocomp failing to build. > > > > My last build is from april 12 (well...) and it does include the > > tomsmocomp filter. I use 3.4.3 though. > > yeah, I only have problems with gcc4. > > I think I'll just disable tomsmocomp if gcc4 is detected, unless > someone says it works for them ... I don't know what gcc4 changed WRT mmx registers... I'll ask our local gcc guru. Thanks Matthias -- Matthias Hopf <mhopf@xxxxxxx> __ __ __ Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat@xxxxxxxxx Phone +49-911-74053-715 __) |_| __) |__ labs www.mshopf.de

Next Message by Date: click to view message preview

Re: filter_tomsmocomp && gcc4

On Mon, Jul 04, 2005 at 04:08:02PM +0200, Matthias Hopf wrote: > On Jul 02, 05 13:25:10 -0700, Jacob Meuser wrote: > > the tomsmocomp filter doesn't build for me with > > > > gcc version 4.0.1 20050609 (prerelease) > > > > > > egcc -DHAVE_CONFIG_H -I. > > -I/sandbox/portobj/transcode-1.0.0rc1/transcode-1.0.0r > > c1/filter/tomsmocomp -I../.. -D_REENTRANT > > -I/sandbox/portobj/transcode-1.0.0rc1/ > > transcode-1.0.0rc1 > > -I/sandbox/portobj/transcode-1.0.0rc1/transcode-1.0.0rc1/src > > -I/sandbox/portobj/transcode-1.0.0rc1/transcode-1.0.0rc1/aclib > > -I/usr/local/incl > > ude -I/usr/X11R6/include -fno-omit-frame-pointer -Wall -D_LARGEFILE_SOURCE > > -D_LA > > RGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -pipe -Wall -MT > > tomsmocompfilter_mmx > > .lo -MD -MP -MF .deps/tomsmocompfilter_mmx.Tpo -c > > /sandbox/portobj/transcode-1.0 > > .0rc1/transcode-1.0.0rc1/filter/tomsmocomp/tomsmocompfilter_mmx.c -fPIC > > -DPIC - > > o .libs/tomsmocompfilter_mmx.o > > /sandbox/portobj/transcode-1.0.0rc1/transcode-1.0.0rc1/filter/tomsmocomp/SearchL > > oopTop.inc: In function 'filterDScaler_MMX': > > /sandbox/portobj/transcode-1.0.0rc1/transcode-1.0.0rc1/filter/tomsmocomp/SearchL > > oopTop.inc:91: error: unknown register name 'mm7' in 'asm' > > I now have the culprit - you have to explicitely specify -mmmx in order > to be able to use inline mmx assembly. > > As this changes the code generation of standard code as well, we cannot > plainly add -mmmx -msse -msse2 etc. to CFLAGS, but instead we would have > to add these flags for the according files only (in order to still allow > for runtime decision). > > AFAIK this is something that is lively debated on the gcc mailing lists, > so there might be a change soon. I don't want to explicitly add > something right now until this is setteled. Maybe deselecting > tomsmocomp for gcc 4.0 is not a bad solution right now. OK, that is what I have done. I don't want to add some new code right before the release, and there probably aren't all that many people (hopefully) using gcc4 just yet. -- <jakemsr@xxxxxxxxxxx>

Previous Message by Thread: click to view message preview

Re: filter_tomsmocomp && gcc4

On Jul 03, 05 14:39:52 -0700, Jacob Meuser wrote: > On Sun, Jul 03, 2005 at 12:29:10PM +0200, Erik Slagter wrote: > > On Sat, 2005-07-02 at 13:25 -0700, Jacob Meuser wrote: > > > the tomsmocomp filter doesn't build for me with > > > > > has anyone else seen this? I don't remember seeing a report about > > > tomsmocomp failing to build. > > > > My last build is from april 12 (well...) and it does include the > > tomsmocomp filter. I use 3.4.3 though. > > yeah, I only have problems with gcc4. > > I think I'll just disable tomsmocomp if gcc4 is detected, unless > someone says it works for them ... I don't know what gcc4 changed WRT mmx registers... I'll ask our local gcc guru. Thanks Matthias -- Matthias Hopf <mhopf@xxxxxxx> __ __ __ Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat@xxxxxxxxx Phone +49-911-74053-715 __) |_| __) |__ labs www.mshopf.de

Next Message by Thread: click to view message preview

Re: filter_tomsmocomp && gcc4

On Mon, Jul 04, 2005 at 04:08:02PM +0200, Matthias Hopf wrote: > On Jul 02, 05 13:25:10 -0700, Jacob Meuser wrote: > > the tomsmocomp filter doesn't build for me with > > > > gcc version 4.0.1 20050609 (prerelease) > > > > > > egcc -DHAVE_CONFIG_H -I. > > -I/sandbox/portobj/transcode-1.0.0rc1/transcode-1.0.0r > > c1/filter/tomsmocomp -I../.. -D_REENTRANT > > -I/sandbox/portobj/transcode-1.0.0rc1/ > > transcode-1.0.0rc1 > > -I/sandbox/portobj/transcode-1.0.0rc1/transcode-1.0.0rc1/src > > -I/sandbox/portobj/transcode-1.0.0rc1/transcode-1.0.0rc1/aclib > > -I/usr/local/incl > > ude -I/usr/X11R6/include -fno-omit-frame-pointer -Wall -D_LARGEFILE_SOURCE > > -D_LA > > RGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -pipe -Wall -MT > > tomsmocompfilter_mmx > > .lo -MD -MP -MF .deps/tomsmocompfilter_mmx.Tpo -c > > /sandbox/portobj/transcode-1.0 > > .0rc1/transcode-1.0.0rc1/filter/tomsmocomp/tomsmocompfilter_mmx.c -fPIC > > -DPIC - > > o .libs/tomsmocompfilter_mmx.o > > /sandbox/portobj/transcode-1.0.0rc1/transcode-1.0.0rc1/filter/tomsmocomp/SearchL > > oopTop.inc: In function 'filterDScaler_MMX': > > /sandbox/portobj/transcode-1.0.0rc1/transcode-1.0.0rc1/filter/tomsmocomp/SearchL > > oopTop.inc:91: error: unknown register name 'mm7' in 'asm' > > I now have the culprit - you have to explicitely specify -mmmx in order > to be able to use inline mmx assembly. > > As this changes the code generation of standard code as well, we cannot > plainly add -mmmx -msse -msse2 etc. to CFLAGS, but instead we would have > to add these flags for the according files only (in order to still allow > for runtime decision). > > AFAIK this is something that is lively debated on the gcc mailing lists, > so there might be a change soon. I don't want to explicitly add > something right now until this is setteled. Maybe deselecting > tomsmocomp for gcc 4.0 is not a bad solution right now. OK, that is what I have done. I don't want to add some new code right before the release, and there probably aren't all that many people (hopefully) using gcc4 just yet. -- <jakemsr@xxxxxxxxxxx>