public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/109776] [14 Regression] pr81192 fails on some targets after recent propagator changes
Date: Mon, 08 May 2023 17:43:23 +0000 [thread overview]
Message-ID: <bug-109776-4-nldO2Jz0rC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109776-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109776
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |pinskia at gcc dot gnu.org
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #3)
> The issue is xstormy has a 16bit int type and both 1 and 0 are getting
> assigned
> 'int'.
>
> Since you #define int you need to wrap all literals with _Literal (int) ...
> and of course 2147483647 won't fit (thus dg-require-effective-target
> int32plus?)
Oh I missed the define for some reason when I was looking into the tests today.
Let me try to fix it for 16bit int targets.
next prev parent reply other threads:[~2023-05-08 17:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 16:41 [Bug testsuite/109776] New: " law at gcc dot gnu.org
2023-05-08 16:57 ` [Bug testsuite/109776] " pinskia at gcc dot gnu.org
2023-05-08 16:58 ` pinskia at gcc dot gnu.org
2023-05-08 17:39 ` rguenth at gcc dot gnu.org
2023-05-08 17:43 ` pinskia at gcc dot gnu.org [this message]
2023-05-08 18:04 ` cvs-commit at gcc dot gnu.org
2023-05-08 18:06 ` pinskia at gcc dot gnu.org
2023-05-08 18:31 ` law 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-109776-4-nldO2Jz0rC@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).