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 target/105647] New test g++.dg/modules/pr105169 from r13-566-g7a3f38a966a528 fails with assembler error
Date: Thu, 19 May 2022 13:01:14 +0000 [thread overview]
Message-ID: <bug-105647-4-lrTmVEOTgx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105647-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105647
--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Giuliano Belinassi
<giulianob@gcc.gnu.org>:
https://gcc.gnu.org/g:16e02662c092c6e3087628ef0030e7daa2f71485
commit r13-633-g16e02662c092c6e3087628ef0030e7daa2f71485
Author: Giuliano Belinassi <gbelinassi@suse.de>
Date: Wed May 18 16:16:48 2022 -0300
PR105647 Update pr105169* so it does not fail on powerpc64le
On powerpc64le, the tests related to pr105169 failed because the
.localentry was not on a power of two address due to the extra nop
instruction taking one byte and thus moving its position one byte
further. Generating two nops instead moves .localentry to a valid
position.
gcc/testsuite/ChangeLog
2022-05-18 Giuliano Belinassi <gbelinassi@suse.de>
PR target/105647
* g++.dg/modules/pr105169_a.C: Change -fpatchable-function-entry to
2.
* g++.dg/modules/pr105169_b.C: Likewise.
prev parent reply other threads:[~2022-05-19 13:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 14:33 [Bug other/105647] New: " seurer at gcc dot gnu.org
2022-05-18 15:47 ` [Bug target/105647] " giuliano.belinassi at gmail dot com
2022-05-19 6:11 ` rguenth at gcc dot gnu.org
2022-05-19 13:01 ` cvs-commit at gcc dot gnu.org [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=bug-105647-4-lrTmVEOTgx@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).