On Tue, May 26, 2020 at 6:49 AM Jakub Jelinek via Gcc-patches
wrote:
>
> Hi!
>
> I've turned the strict mode of Martin Liška's hook changes,
> which means that from now on no commits to the trunk or release branches
> should be changing any ChangeLog files together with the other files,
> ChangeLo
Great, thanks!
On Tue, May 26, 2020 at 2:08 PM Martin Liška wrote:
>
> On 5/26/20 7:22 AM, Hongtao Liu via Gcc wrote:
> > i commit a separate patch alone only for ChangeLog files, should i revert
> > it?
>
> Hello.
>
> I've just done it.
>
> Martin
--
BR,
Hongtao
On Mon, Dec 7, 2020 at 5:47 PM Richard Biener wrote:
>
> On Mon, 7 Dec 2020, Prathamesh Kulkarni wrote:
>
> > On Mon, 7 Dec 2020 at 13:01, Richard Biener wrote:
> > >
> > > On Mon, 7 Dec 2020, Prathamesh Kulkarni wrote:
> > >
> > > > On Fri, 4 Dec 2020 at 17:18, Richard Biener wrote:
> > > > >
>
On Mon, Dec 7, 2020 at 7:11 PM Prathamesh Kulkarni
wrote:
>
> On Mon, 7 Dec 2020 at 16:15, Hongtao Liu wrote:
> >
> > On Mon, Dec 7, 2020 at 5:47 PM Richard Biener wrote:
> > >
> > > On Mon, 7 Dec 2020, Prathamesh Kulkarni wrote:
> > >
> > > > On Mon, 7 Dec 2020 at 13:01, Richard Biener wrote:
It seems better with your PR97872 fix on i386.
Cat test.c
typedef char v16qi __attribute__ ((vector_size(16)));
v16qi f1(v16qi a, v16qi b) {
return (a & b) != 0;
}
before
f1(char __vector(16), char __vector(16)):
pand %xmm1, %xmm0
pxor %xmm1, %xmm1
pcmpeqb %xmm1, %xmm0
pcmpeqd %xmm1, %xmm1
pand
On Tue, Jun 22, 2021 at 3:58 PM Jakub Jelinek via Gcc wrote:
>
> On Mon, Jun 21, 2021 at 02:49:56AM +, Liu, Hongtao via Gcc wrote:
> > >-Original Message-
> > >From: Jason Merrill
> > >Sent: Monday, June 21, 2021 10:07 AM
> > >To: Liu, Hongtao
> > >Cc: gcc Mailing List ; Marek Polace
Hi:
The original problem was that some users wanted the cmdline option
-ffast-math not to act on intrinsic production code. .i.e for codes
like
#include
__m256d
foo2 (__m256d a, __m256d b, __m256d c, __m256d d)
{
__m256d tmp = _mm256_add_pd (a, b);
tmp = _mm256_sub_pd (tmp, c);
tmp = _mm256_sub_
On Wed, Jul 14, 2021 at 1:15 PM Hongtao Liu wrote:
>
> Hi:
> The original problem was that some users wanted the cmdline option
> -ffast-math not to act on intrinsic production code. .i.e for codes
> like
>
> #include
> __m256d
> foo2 (__m256d a, __m256d b, __m256d c, __m256d d)
> {
> __m256d tm
On Wed, Jul 14, 2021 at 2:39 PM Matthias Kretz wrote:
>
> On Wednesday, 14 July 2021 07:18:29 CEST Hongtao Liu via Gcc-help wrote:
> > On Wed, Jul 14, 2021 at 1:15 PM Hongtao Liu wrote:
> > > Hi:
> > > The original problem was that some users wanted the cmdline
On Wed, Jul 14, 2021 at 3:49 PM Matthias Kretz wrote:
>
> On Wednesday, 14 July 2021 09:39:42 CEST Richard Biener wrote:
> > -ffast-math decomposes to quite some flag_* and those generally are not
> > reflected into the IL but can be different per function (and then
> > prevent inlining).
>
> Is t
On Wed, Jul 14, 2021 at 4:17 PM Richard Biener
wrote:
>
> On Wed, Jul 14, 2021 at 10:11 AM Hongtao Liu wrote:
> >
> > On Wed, Jul 14, 2021 at 3:49 PM Matthias Kretz wrote:
> > >
> > > On Wednesday, 14 July 2021 09:39:42 CEST Richard Biener wrote:
> > > > -ffast-math decomposes to quite some flag
On Thu, Jul 29, 2021 at 10:49 AM unlvsur unlvsur via Gcc
wrote:
>
> What I mean is that what macro GCC sets when it compiles -masm=intel
>
>
> Int main()
> {
> #ifdef /*__INTEL_ASM*/
> printf(“intel”);
> #else
> printf(“at&t”);
> #endif
> }
not fully understand
Could you file a bugzilla for that?
https://gcc.gnu.org/bugzilla/enter_bug.cgi?product=gcc
On Thu, Aug 5, 2021 at 3:34 PM Stefan Kanthak wrote:
>
> Hi,
>
> targeting AMD64 alias x86_64 with -O3, GCC 10.2.0 generates the
> following code (17 instructions using 78 bytes, plus 6 quadwords
> using 48
On Thu, Aug 5, 2021 at 5:20 AM Segher Boessenkool
wrote:
>
> On Wed, Aug 04, 2021 at 11:22:53AM +0100, Richard Sandiford wrote:
> > Segher Boessenkool writes:
> > > On Wed, Aug 04, 2021 at 10:10:36AM +0100, Richard Sandiford wrote:
> > >> Richard Biener writes:
> > >> > Alternatively only enable
On Tue, Aug 31, 2021 at 11:11 AM Kewen.Lin via Gcc wrote:
>
> on 2021/8/30 下午10:11, Bill Schmidt wrote:
> > On 8/30/21 8:04 AM, Florian Weimer wrote:
> >> There has been a discussion, both off-list and on the gcc-help mailing
> >> list (“Why vectorization didn't turn on by -O2”, spread across seve
On Wed, Sep 1, 2021 at 7:24 PM Tamar Christina via Gcc wrote:
>
> -- edit, added list back in --
>
> Just to add some AArch64 numbers for Spec2017 we see 2.1% overall Geomean
> improvements (all from x264 as expected) with no real regressions (everything
> within variance) and only a 0.06% binar
gcc define __FLT_EVAL_METHOD__ according to
builtin_define_with_int_value ("__FLT_EVAL_METHOD__",
c_flt_eval_method (true));
and guess we need to handle things like:
/* GCC only supports one interchange type right now, _Float16. If
we're evaluating _Float16 in 16-bit precision, then
On Mon, Feb 7, 2022 at 11:16 AM LiYancheng via Gcc wrote:
>
>
> On 2022/2/7 10:03, Andrew Pinski wrote:
> > On Sun, Feb 6, 2022 at 5:59 PM LiYancheng via Gcc wrote:
> >> Hello everyone!
> >>
> >> I have some questions to ask:
> >>
> >> 1. How does GCC support Sapphrie Rapids CPU now?
> >>
> >> 2.
On Wed, May 24, 2023 at 3:58 PM Jan Beulich via Gcc wrote:
>
> Hello,
>
> for a couple of years I was meaning to extend the use of these AVX512F
> insns beyond the pretty minimalistic ones there are so far. Now that I've
> got around to at least draft something, I ran into a couple of issues I
> c
On Mon, Aug 7, 2023 at 2:08 AM Toon Moene wrote:
>
> Wonder if I am the only one to see this:
>
> https://gcc.gnu.org/pipermail/gcc-testresults/2023-August/792616.html
>
> To quote:
>
> during RTL pass: split1
> /home/toon/compilers/gcc/libgfortran/generated/matmul_i1.c: In function
> 'matmul_i1_a
On Mon, Aug 7, 2023 at 9:35 AM Hongtao Liu wrote:
>
> On Mon, Aug 7, 2023 at 2:08 AM Toon Moene wrote:
> >
> > Wonder if I am the only one to see this:
> >
> > https://gcc.gnu.org/pipermail/gcc-testresults/2023-August/792616.html
Could you share your GCC configure, I guess
--enable-checking=yes,r
On Mon, Aug 7, 2023 at 9:38 AM Hongtao Liu wrote:
>
> On Mon, Aug 7, 2023 at 9:35 AM Hongtao Liu wrote:
> >
> > On Mon, Aug 7, 2023 at 2:08 AM Toon Moene wrote:
> > >
> > > Wonder if I am the only one to see this:
> > >
> > > https://gcc.gnu.org/pipermail/gcc-testresults/2023-August/792616.html
On Fri, May 31, 2024 at 10:58 AM Hanke Zhang via Gcc wrote:
>
> Hi,
> I've recently been trying to hand-write code to trigger automatic
> vectorization optimizations in GCC on Intel x86 machines (without
> using the interfaces in immintrin.h), but I'm running into a problem
> where I can't seem to
23 matches
Mail list logo
