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/99636] [10/11 regression] gcc.dg/strlenopt-80.c fails for 32 bits
Date: Thu, 18 Mar 2021 15:19:17 +0000 [thread overview]
Message-ID: <bug-99636-4-ldLSG8dExK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99636-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99636
--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:89d44a9f3b9ab97634b7ef894e2c83ebd83582a8
commit r11-7719-g89d44a9f3b9ab97634b7ef894e2c83ebd83582a8
Author: Jakub Jelinek <jakub@redhat.com>
Date: Thu Mar 18 16:14:47 2021 +0100
testsuite: Fix up strlenopt-80.c on powerpc [PR99636]
Similar issue as in strlenopt-73.c, various spots in this test rely
on MOVE_MAX >= 8, this time it uses a target selector to pick up a couple
of targets, and all of them but powerpc 32-bit satisfy it, but powerpc
32-bit have MOVE_MAX just 4.
2021-03-18 Jakub Jelinek <jakub@redhat.com>
PR testsuite/99636
* gcc.dg/strlenopt-80.c: For powerpc*-*-*, only enable for lp64.
next prev parent reply other threads:[~2021-03-18 15:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 20:44 [Bug testsuite/99636] New: " seurer at gcc dot gnu.org
2021-03-18 9:04 ` [Bug testsuite/99636] " rguenth at gcc dot gnu.org
2021-03-18 15:19 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-18 15:22 ` [Bug testsuite/99636] [10 Regression] " jakub at gcc dot gnu.org
2021-03-19 23:31 ` cvs-commit at gcc dot gnu.org
2021-03-20 8:10 ` jakub 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-99636-4-ldLSG8dExK@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).