public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/114662] [14 regression] new test case c_lto_pr113359-2 from r14-9841-g1e3312a25a7b34 fails
Date: Wed, 10 Apr 2024 08:01:37 +0000	[thread overview]
Message-ID: <bug-114662-4-Aym1lkYah1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114662-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114662

--- Comment #3 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:

https://gcc.gnu.org/g:4923ed49b93352bcf9e43cafac38345e4a54c3f8

commit r14-9886-g4923ed49b93352bcf9e43cafac38345e4a54c3f8
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Wed Apr 10 02:59:43 2024 -0500

    testsuite: Adjust pr113359-2_*.c with unsigned long long [PR114662]

    pr113359-2_*.c define a struct having unsigned long type
    members ay and az which have 4 bytes size at -m32, while
    the related constants CL1 and CL2 used for equality check
    are always 8 bytes, it makes compiler consider the below

      69   if (a.ay != CL1)
      70     __builtin_abort ();

    always to abort and optimize away the following call to
    getb, which leads to the expected wpa dumping on
    "Semantic equality" missing.

    This patch is to modify the types with unsigned long long
    accordingly.

            PR testsuite/114662

    gcc/testsuite/ChangeLog:

            * gcc.dg/lto/pr113359-2_0.c: Use unsigned long long instead of
            unsigned long.
            * gcc.dg/lto/pr113359-2_1.c: Likewise.

  parent reply	other threads:[~2024-04-10  8:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-09 18:22 [Bug lto/114662] New: " seurer at gcc dot gnu.org
2024-04-09 18:54 ` [Bug lto/114662] " ewlu at rivosinc dot com
2024-04-10  5:56 ` linkw at gcc dot gnu.org
2024-04-10  6:26 ` [Bug testsuite/114662] " linkw at gcc dot gnu.org
2024-04-10  8:01 ` cvs-commit at gcc dot gnu.org [this message]
2024-04-10  8:04 ` linkw at gcc dot gnu.org
2024-04-10  9:24 ` jamborm at gcc dot gnu.org
2024-05-21 15:47 ` cvs-commit at gcc dot gnu.org

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=bug-114662-4-Aym1lkYah1@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).