On Tue, Nov 15, 2016 at 9:36 AM, Andrew Senkevich
wrote:
> Hi,
>
> new Intel instructions AVX512_4FMAPS and AVX512_4VNNIW introduce use
> of register groups.
>
> To support register groups feature in inline asm needed some extension
> with new constraints.
>
> Current proposal is the following syn
Many of the GCC features listed here are not mentioned in
gcc-7/changes.html. We all need to expand that to be more thorough in
covering features that are new in GCC 7 compared to GCC 6.
--
Joseph S. Myers
jos...@codesourcery.com
Snapshot gcc-5-20161115 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/5-20161115/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 5 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-5
Hi,
new Intel instructions AVX512_4FMAPS and AVX512_4VNNIW introduce use
of register groups.
To support register groups feature in inline asm needed some extension
with new constraints.
Current proposal is the following syntax:
__asm__ (“SMTH %[group], %[single]" :
Hi Guys,
Long time, no post. Sorry about that. So, in order to make up for
it, here is an extra long update on the state of the GNU toolchain:
In GCC land, 6.2 has now been released and GCC 7 is almost ready to
branch. Here are the new features that you can expect to find in
GCC 7:
On Tue, Nov 15, 2016 at 1:38 PM, Thomas Koenig wrote:
> Hi,
>
> I ran some testing on the soon-to-be-committed matmul patch.
> Specifically, I tried out what putting -march=native into
> libgfortran's Makefile.
>
> Here is the performance data with the new code without -march.
> The interesting nu
I ran some testing on the soon-to-be-committed matmul patch.
Specifically, I tried out what putting -march=native into
libgfortran's Makefile.
I should have added that this was for a system with AVX
(namely an i7-2600).
Hi,
I ran some testing on the soon-to-be-committed matmul patch.
Specifically, I tried out what putting -march=native into
libgfortran's Makefile.
Here is the performance data with the new code without -march.
The interesting numbers are the ones for Matml fixed explicit,
for size>=32.
===
Hi,
On Mon, Nov 14, 2016 at 09:45:49AM -0800, Cesar Philippidis wrote:
> What's the plan to split omp-low.c into multiple files? Right now,
> omp-low.c contains code to lower and expand OpenMP and OpenACC. At least
> for the OpenACC transforms, we made an effort to keep the changes in
> omp-low.c
