This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: alsa-lib 1.0.2 -fPIC problem with gcc 3.4


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday 08 February 2004 16:07, you wrote:
> Jan Killius <jkillius@arcor.de> writes:
> > On Sunday 08 February 2004 14:12, you wrote:
> > > Jan Killius <jkillius@arcor.de> writes:
> > > > there seems to be a problem with the assembler code and -fPIC. My
> > > > question is, it is a gcc problem or a code problem. And how we can
> > > > solve it ?
> > >
> > > Gcc inline assembly is not designed for whole functions. Best would be
> > > to simply put the code into a .s file and compile it seperately. That
> > > would also improve readability.
> > >
> > > If you absolutely have to use inline assembly (I don't see any reason,
> > > but some people seem to fanatically insist on it), save and restore
> > > the PIC register manually inside the asm and don't mark it as
> > > clobbered.
> >
> > I have googled around a bit and found this solution:
> > "\tpushl %%ebx\n"
> > // thecode
> > "\tpopl %%ebx\n"
> > But i got the same error message...
>
> So why don't you just put the code in a .s file then? :-)
>
> But if you *still* insist, as I said, you need to remove the clobber
> of ebx.
The code need many changes to put it in a .s file and I'm not very good at 
assembler. To remove the clobber I must change the register or not ? But 
how ?
- -- 
        Jan Killius
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAJlX/6U6IB8YmOOwRAkF/AJ4uHJMo0ANK2dLryrdPsnSh1bvHcgCcDPA/
a3FEg9/EVusHNuHUPjCNMvo=
=Eel8
-----END PGP SIGNATURE-----


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]