public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/106216] New: new test case gcc.dg/tree-ssa/alias-access-path-13.c fails for 32 bits
Date: Wed, 06 Jul 2022 17:47:58 +0000	[thread overview]
Message-ID: <bug-106216-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 106216
           Summary: new test case gcc.dg/tree-ssa/alias-access-path-13.c
                    fails for 32 bits
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: other
          Assignee: unassigned at gcc dot gnu.org
          Reporter: seurer at gcc dot gnu.org
  Target Milestone: ---

g:b110e5283e368b5377e04766e4ff82cd52634208, r13-1460-gb110e5283e368b

This test is failing on 32 bit big endian powerpc64.

make  -k check-gcc RUNTESTFLAGS="--target_board=unix'{-m32}'
tree-ssa.exp=gcc.dg/tree-ssa/alias-access-path-13.c"
FAIL: gcc.dg/tree-ssa/alias-access-path-13.c scan-tree-dump-times fre1 "return
123" 1
# of expected passes            1
# of unexpected failures        1


commit b110e5283e368b5377e04766e4ff82cd52634208
Author: Martin Jambor <mjambor@suse.cz>
Date:   Fri Jul 1 20:57:18 2022 +0200

    tree-sra: Fix union handling in build_reconstructed_reference

             reply	other threads:[~2022-07-06 17:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-06 17:47 seurer at gcc dot gnu.org [this message]
2022-07-06 19:47 ` [Bug other/106216] " jamborm at gcc dot gnu.org
2022-07-08 16:14 ` [Bug testsuite/106216] " cvs-commit at gcc dot gnu.org
2022-07-08 16:22 ` jamborm 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-106216-4@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).