This is the mail archive of the gcc-patches@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: [PATCH] Update support patch for ACML vectorized intrinsic library

From: Paolo Bonzini <bonzini at gnu dot org>
To: Richard Guenther <rguenther at suse dot de>
Cc: Uros Bizjak <ubizjak at gmail dot com>, GCC Patches <gcc-patches at gcc dot gnu dot org>, Jan Hubicka <jh at suse dot cz>
Date: Fri, 24 Aug 2007 13:45:39 +0200
Subject: Re: [PATCH] Update support patch for ACML vectorized intrinsic library
References: <46C9EF2C.8000808@gmail.com> <Pine.LNX.4.64.0708211434220.13885@s68.fhfr.qr> <Pine.LNX.4.64.0708241257480.4343@s68.fhfr.qr> <5787cf470708240402u1bb79c56k5f0955d784c6e6fd@mail.gmail.com> <Pine.LNX.4.64.0708241311000.4343@s68.fhfr.qr>

So I am fine with either of two options - not linking automatically
or linking against libacml_mv with -mveclib=acml.

What about having -mveclibabi=acml doing what it does now, and -mveclib=acml doing "-mveclibabi=acml -lacml_mv"? Which you could also read as, link automatically with libacml_mv and make a note to implement -mveclibabi when the need arises...

Paolo

Follow-Ups:
- Re: [PATCH] Update support patch for ACML vectorized intrinsic library
  - From: Uros Bizjak

References:
- Re: [PATCH] Update support patch for ACML vectorized intrinsic library
  - From: Uros Bizjak
- Re: [PATCH] Update support patch for ACML vectorized intrinsic library
  - From: Richard Guenther
- Re: [PATCH] Update support patch for ACML vectorized intrinsic library
  - From: Richard Guenther
- Re: [PATCH] Update support patch for ACML vectorized intrinsic library
  - From: Uros Bizjak
- Re: [PATCH] Update support patch for ACML vectorized intrinsic library
  - From: Richard Guenther

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