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/114182] gcc.c-torture/compile/attr-complex-method-2.c fails for H8/300
Date: Fri, 01 Mar 2024 00:58:06 +0000 [thread overview]
Message-ID: <bug-114182-4-YFXE03r43f@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114182-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114182
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
Keywords| |testsuite-fail
Last reconfirmed| |2024-03-01
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Most likely it would be better to have a target support proc that returns if
`double == float` and use that.
Oh there is large_double already. You should just use that instead.
So just:
/* { dg-final { scan-tree-dump "__(?:gnu_)?divdc3" "optimized" { target { ! {
large_double } } } } } */
/* { dg-final { scan-tree-dump "__(?:gnu_)?divsc3" "optimized" { target {
large_double } } } } */
>Similarly, shouldn't attr-complex-method.c also search for __divsc3 for AVR, H8/300 and possibly a few other architectures?
Most likely yes.
next prev parent reply other threads:[~2024-03-01 0:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 0:34 [Bug testsuite/114182] New: " jdx at o2 dot pl
2024-03-01 0:58 ` pinskia at gcc dot gnu.org [this message]
2024-03-03 17:42 ` [Bug testsuite/114182] " jdx at o2 dot pl
2024-03-04 1:12 ` jdx at o2 dot pl
2024-03-04 1:16 ` pinskia at gcc dot gnu.org
2024-03-08 22:32 ` 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-114182-4-YFXE03r43f@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).