2008/11/5 Jonathan Grant <[EMAIL PROTECTED]>:
> Hi Karl,
>
> Thank you for your reply
>
> [..]
>> If some examples use @example and some examples use @smallexample, the
>> resulting inconsistency looks quite bad as well (in both printed manuals
>> and HTML).
>>
>> I doubt the GCC folks want to rese
Hi Karl,
Thank you for your reply
[..]
> If some examples use @example and some examples use @smallexample, the
> resulting inconsistency looks quite bad as well (in both printed manuals
> and HTML).
>
> I doubt the GCC folks want to research and rewrite their examples to use
> shorter lines (so
Hi HJ,
On Mon, 3 Nov 2008, H.J. Lu wrote:
> Icc will introduce to support intrinsics for current and
> future instruction sets, starting with AVX.
So how about the (IMO) nicer name this list came up the last time this was
brought up (April): x86intrin.h .
> My question is if we should put AV
I agree with Michael on the naming and having separate files for AVX and
including all the header files inside x86intrin.h.
Also it would be easy for the users if we include all the instruction
sets supported by both Intel and AMD in x86intrin.h file so that it is
sufficient for the application de
On Wed, Nov 5, 2008 at 7:38 AM, rajagopal, dwarak
<[EMAIL PROTECTED]> wrote:
> I agree with Michael on the naming and having separate files for AVX and
> including all the header files inside x86intrin.h.
>
> Also it would be easy for the users if we include all the instruction
> sets supported by
Snapshot gcc-4.2-20081105 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.2-20081105/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.2 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
