public inbox for gcc-regression@sourceware.org
help / color / mirror / Atom feed
From: Andrew MacLeod <amacleod@redhat.com>
To: "sunil.k.pandey" <skpandey@sc.intel.com>,
	gcc-patches@gcc.gnu.org, gcc-regression@gcc.gnu.org
Subject: Re: [r12-4413 Regression] FAIL: gcc.dg/pr102738.c (test for excess errors) on Linux/x86_64
Date: Thu, 14 Oct 2021 20:39:37 -0400	[thread overview]
Message-ID: <59ab5113-26c0-4e1f-cf67-6909f1ea3543@redhat.com> (raw)
In-Reply-To: <20211015001923.E2FC8286470F@gskx-2.sc.intel.com>

On 10/14/21 8:19 PM, sunil.k.pandey wrote:
> On Linux/x86_64,
>
> f0b7d4cc49ddb1c2c7474cc3f61e260aa93a96c0 is the first bad commit
> commit f0b7d4cc49ddb1c2c7474cc3f61e260aa93a96c0
> Author: Andrew MacLeod <amacleod@redhat.com>
> Date:   Thu Oct 14 10:43:58 2021 -0400
>
>      Simplification for right shift.
>
> caused
>
> FAIL: gcc.dg/pr102738.c (test for excess errors)
>
> with GCC configured with
>
> ../../gcc/configure --prefix=/local/skpandey/gccwork/toolwork/gcc-bisect-master/master/r12-4413/usr --enable-clocale=gnu --with-system-zlib --with-demangler-in-ld --with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet --without-isl --enable-libmpx x86_64-linux --disable-bootstrap
>
> To reproduce:
>
> $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/pr102738.c --target_board='unix{-m32}'"
> $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/pr102738.c --target_board='unix{-m32\ -march=cascadelake}'"
>
> (Please do not reply to this email, for question about this report, contact me at skpgkp2 at gmail dot com)
>
Is this due to lack of 128 bit support?   that fix has just been checked 
in and I think resolves it...

Sorry

Andrew



      reply	other threads:[~2021-10-15  0:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-15  0:19 sunil.k.pandey
2021-10-15  0:39 ` Andrew MacLeod [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=59ab5113-26c0-4e1f-cf67-6909f1ea3543@redhat.com \
    --to=amacleod@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc-regression@gcc.gnu.org \
    --cc=skpandey@sc.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).