mesa3d-dev

[Mesa3d-dev] CVS and SSE

[Allen B. <ba...@lo...>]

Hi,

Yesterday (4/27), I pulled the current CVS version of Mesa. I was hoping
to be able to activate the Intel SSE commands, however the configuration
script tries a test assenble on the file src/X86/katmai_xform_raw3.S,
which does not exist. It looks like the configure script is somewhat out
of sync with the current contents of src/X86/. Is there a simple change
I can make to configure or should I just pull an earlier (3.4.1?)
version of the CVS tree? (The corresponding files do appear in the
XFree86 DRI Mesa source.)

Thanks,
Allen

Re: [Mesa3d-dev] CVS and SSE

[Brian P. <br...@va...>]

Allen Barnett wrote:
> 
> Hi,
> 
> Yesterday (4/27), I pulled the current CVS version of Mesa. I was hoping
> to be able to activate the Intel SSE commands, however the configuration
> script tries a test assenble on the file src/X86/katmai_xform_raw3.S,
> which does not exist. It looks like the configure script is somewhat out
> of sync with the current contents of src/X86/. Is there a simple change
> I can make to configure or should I just pull an earlier (3.4.1?)
> version of the CVS tree? (The corresponding files do appear in the
> XFree86 DRI Mesa source.)

I was trying to fix this a few days ago but got stuck.  Your clue
about the test assemble of src/X86/katmai_xform_raw3.S helped me find
the problem now.  I'm about to check in some updates that should fix
this.

One problem is still outstanding.  The src/X86/gen_matypes.c file must
be compiled and executed in order to generate src/X86/matypes.h before
the assembly code can be compiled.  You can do this manually:

	cd src/X86
	gcc gen_matypes.c -I.. -I../../include -o gen_matypes
	./gen_matypes > matypes.h

I don't know how to make configure do this.  When I make the MesaLib-3.5
tarballs I'll include matypes.h so it won't be a problem for typical end
users.  We developers and CVS users just have to remember to regenerate
matypes.h whenever src/mtypes.h changes.

I'll check in my updates ASAP.

-Brian

Re: [Mesa3d-dev] CVS and SSE

[Sven M. H. <pe...@gm...>]

On Fri, Apr 27, 2001 at 09:59:03AM -0600, Brian Paul wrote:
> Allen Barnett wrote:
> > 
> > Hi,
> > 
> > Yesterday (4/27), I pulled the current CVS version of Mesa. I was hoping
> > to be able to activate the Intel SSE commands, however the configuration
> > script tries a test assenble on the file src/X86/katmai_xform_raw3.S,
> > which does not exist. It looks like the configure script is somewhat out
> > of sync with the current contents of src/X86/. Is there a simple change
> > I can make to configure or should I just pull an earlier (3.4.1?)
> > version of the CVS tree? (The corresponding files do appear in the
> > XFree86 DRI Mesa source.)
> 
> I was trying to fix this a few days ago but got stuck.  Your clue
> about the test assemble of src/X86/katmai_xform_raw3.S helped me find
> the problem now.  I'm about to check in some updates that should fix
> this.
> 
> One problem is still outstanding.  The src/X86/gen_matypes.c file must
> be compiled and executed in order to generate src/X86/matypes.h before
> the assembly code can be compiled.  You can do this manually:
> 
> 	cd src/X86
> 	gcc gen_matypes.c -I.. -I../../include -o gen_matypes
> 	./gen_matypes > matypes.h
> 
> I don't know how to make configure do this.  When I make the MesaLib-3.5
> tarballs I'll include matypes.h so it won't be a problem for typical end
> users.  We developers and CVS users just have to remember to regenerate
> matypes.h whenever src/mtypes.h changes.
> 
> I'll check in my updates ASAP.
> 
> -Brian

I will have a look at the new matypes.h stuff (hopefully) soon. Brian, can you
give a (really) brief overview (pseudo-script or whatever) describing how the
steps needed to generate matypes.h?


-Sven

PS: Yes, I am alive. I've just finished my service in the Army and are now
running on spare time for a couple of months. Right now I'm wading through the
last 150 CVS commit messages I've missed. :) Just to let everyone know...

-- 
"Would the All-Seeing Eye please look in my direction?"
 [ KeyID........: 0xC297FEAB ]
 [ Fingerprint..: FEA5 0F93 7320 3F39 66A5  AED3 073F 2D5F C297 FEAB ]

Re: [Mesa3d-dev] CVS and SSE

[Brian P. <br...@va...>]

"Sven M. Hallberg" wrote:
> 
> On Fri, Apr 27, 2001 at 09:59:03AM -0600, Brian Paul wrote:
> > Allen Barnett wrote:
> > >
> > > Hi,
> > >
> > > Yesterday (4/27), I pulled the current CVS version of Mesa. I was hoping
> > > to be able to activate the Intel SSE commands, however the configuration
> > > script tries a test assenble on the file src/X86/katmai_xform_raw3.S,
> > > which does not exist. It looks like the configure script is somewhat out
> > > of sync with the current contents of src/X86/. Is there a simple change
> > > I can make to configure or should I just pull an earlier (3.4.1?)
> > > version of the CVS tree? (The corresponding files do appear in the
> > > XFree86 DRI Mesa source.)
> >
> > I was trying to fix this a few days ago but got stuck.  Your clue
> > about the test assemble of src/X86/katmai_xform_raw3.S helped me find
> > the problem now.  I'm about to check in some updates that should fix
> > this.
> >
> > One problem is still outstanding.  The src/X86/gen_matypes.c file must
> > be compiled and executed in order to generate src/X86/matypes.h before
> > the assembly code can be compiled.  You can do this manually:
> >
> >       cd src/X86
> >       gcc gen_matypes.c -I.. -I../../include -o gen_matypes
> >       ./gen_matypes > matypes.h
> >
> > I don't know how to make configure do this.  When I make the MesaLib-3.5
> > tarballs I'll include matypes.h so it won't be a problem for typical end
> > users.  We developers and CVS users just have to remember to regenerate
> > matypes.h whenever src/mtypes.h changes.
> >
> > I'll check in my updates ASAP.
> >
> > -Brian
> 
> I will have a look at the new matypes.h stuff (hopefully) soon. Brian, can you
> give a (really) brief overview (pseudo-script or whatever) describing how the
> steps needed to generate matypes.h?

I did above.  But really, I'm not sure this is too important.  When
3.5 is released it'll include the matypes.h file.  It's just when
people download from CVS that they have to make/update the matypes.h
file.


> PS: Yes, I am alive. I've just finished my service in the Army and are now
> running on spare time for a couple of months. Right now I'm wading through the
> last 150 CVS commit messages I've missed. :) Just to let everyone know...

OK.

-Brian

Re: [Mesa3d-dev] CVS and SSE

[Sven M. H. <pe...@gm...>]

On Sun, Apr 29, 2001 at 05:14:47PM -0600, Brian Paul wrote:
> > > One problem is still outstanding.  The src/X86/gen_matypes.c file must
> > > be compiled and executed in order to generate src/X86/matypes.h before
> > > the assembly code can be compiled.  You can do this manually:
> > >
> > >       cd src/X86
> > >       gcc gen_matypes.c -I.. -I../../include -o gen_matypes
> > >       ./gen_matypes > matypes.h
> > >
> > > I don't know how to make configure do this.  When I make the MesaLib-3.5
> > > tarballs I'll include matypes.h so it won't be a problem for typical end
> > > users.  We developers and CVS users just have to remember to regenerate
> > > matypes.h whenever src/mtypes.h changes.
> > >
> > > I'll check in my updates ASAP.
> > >
> > > -Brian
> > 
> > I will have a look at the new matypes.h stuff (hopefully) soon. Brian, can you
> > give a (really) brief overview (pseudo-script or whatever) describing how the
> > steps needed to generate matypes.h?
> 
> I did above.  But really, I'm not sure this is too important.  When
> 3.5 is released it'll include the matypes.h file.  It's just when
> people download from CVS that they have to make/update the matypes.h
> file.

Ooops. Sorry, too tired by all those mails.


-- 
"Would the All-Seeing Eye please look in my direction?"
 [ KeyID........: 0xC297FEAB ]
 [ Fingerprint..: FEA5 0F93 7320 3F39 66A5  AED3 073F 2D5F C297 FEAB ]

Re: [Mesa3d-dev] CVS and SSE

[Sven M. H. <pe...@gm...>]

On Fri, Apr 27, 2001 at 09:59:03AM -0600, Brian Paul wrote:
> One problem is still outstanding.  The src/X86/gen_matypes.c file must
> be compiled and executed in order to generate src/X86/matypes.h before
> the assembly code can be compiled.  You can do this manually:
> 
> 	cd src/X86
> 	gcc gen_matypes.c -I.. -I../../include -o gen_matypes
> 	./gen_matypes > matypes.h
> 
> I don't know how to make configure do this.  When I make the MesaLib-3.5
> tarballs I'll include matypes.h so it won't be a problem for typical end
> users.  We developers and CVS users just have to remember to regenerate
> matypes.h whenever src/mtypes.h changes.

Woohoo! This is done all nice and clean now! :) (Can you tell I'm proud?)

src/X86/Makefile.am now includes a rule for building gen_matypes, one for
generating matypes.h through it, as well as the dependency on matypes.h.
Means: everything is done automagically once it is needed.

Unfortunately the configure script depended on matypes.h in the checks for
MMX etc. :o.

I built small checks for all the assembler features in m4/assembler.m4 using
just one instruction of the particular command set each. On my system this
reports all command sets as available. However assembly is not my focus, so
someone more comfortable with all that migh want to double-check the test
cases.

-Sven

-- 
"Would the All-Seeing Eye please look in my direction?"
 [ KeyID........: 0xC297FEAB ]
 [ Fingerprint..: FEA5 0F93 7320 3F39 66A5  AED3 073F 2D5F C297 FEAB ]