public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jdx at o2 dot pl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/114182] New: gcc.c-torture/compile/attr-complex-method-2.c fails for H8/300 Date: Fri, 01 Mar 2024 00:34:03 +0000 [thread overview] Message-ID: <bug-114182-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114182 Bug ID: 114182 Summary: gcc.c-torture/compile/attr-complex-method-2.c fails for H8/300 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsuite Assignee: unassigned at gcc dot gnu.org Reporter: jdx at o2 dot pl Target Milestone: --- Host: x86_64-pc-linux-gnu Target: h8300-elf Created attachment 57581 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57581&action=edit Dump file for attr-complex-method-2.c [...] PASS: gcc.c-torture/compile/attr-complex-method-2.c -O0 (test for excess errors) FAIL: gcc.c-torture/compile/attr-complex-method-2.c -O0 scan-tree-dump optimized "__(?:gnu_)?divdc3" PASS: gcc.c-torture/compile/attr-complex-method-2.c -O1 (test for excess errors) FAIL: gcc.c-torture/compile/attr-complex-method-2.c -O1 scan-tree-dump optimized "__(?:gnu_)?divdc3" PASS: gcc.c-torture/compile/attr-complex-method-2.c -O2 (test for excess errors) FAIL: gcc.c-torture/compile/attr-complex-method-2.c -O2 scan-tree-dump optimized "__(?:gnu_)?divdc3" PASS: gcc.c-torture/compile/attr-complex-method-2.c -O3 -g (test for excess errors) FAIL: gcc.c-torture/compile/attr-complex-method-2.c -O3 -g scan-tree-dump optimized "__(?:gnu_)?divdc3" PASS: gcc.c-torture/compile/attr-complex-method-2.c -Os (test for excess errors) FAIL: gcc.c-torture/compile/attr-complex-method-2.c -Os scan-tree-dump optimized "__(?:gnu_)?divdc3" UNSUPPORTED: gcc.c-torture/compile/attr-complex-method-2.c -O2 -flto -fno-use-linker-plugin -flto-partition=none UNSUPPORTED: gcc.c-torture/compile/attr-complex-method-2.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects PASS: gcc.c-torture/compile/attr-complex-method.c -O0 (test for excess errors) PASS: gcc.c-torture/compile/attr-complex-method.c -O0 scan-tree-dump-not optimized "__divdc3" PASS: gcc.c-torture/compile/attr-complex-method.c -O1 (test for excess errors) PASS: gcc.c-torture/compile/attr-complex-method.c -O1 scan-tree-dump-not optimized "__divdc3" PASS: gcc.c-torture/compile/attr-complex-method.c -O2 (test for excess errors) PASS: gcc.c-torture/compile/attr-complex-method.c -O2 scan-tree-dump-not optimized "__divdc3" PASS: gcc.c-torture/compile/attr-complex-method.c -O3 -g (test for excess errors) PASS: gcc.c-torture/compile/attr-complex-method.c -O3 -g scan-tree-dump-not optimized "__divdc3" PASS: gcc.c-torture/compile/attr-complex-method.c -Os (test for excess errors) PASS: gcc.c-torture/compile/attr-complex-method.c -Os scan-tree-dump-not optimized "__divdc3" UNSUPPORTED: gcc.c-torture/compile/attr-complex-method.c -O2 -flto -fno-use-linker-plugin -flto-partition=none UNSUPPORTED: gcc.c-torture/compile/attr-complex-method.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects [...] According to the attached dump file, I believe the end of attr-complex-method-2.c should look like this: /* { dg-final { scan-tree-dump "__(?:gnu_)?divdc3" "optimized" { target { ! { avr-*-* h8300-*-* } } } } } */ /* { dg-final { scan-tree-dump "__(?:gnu_)?divsc3" "optimized" { target { avr-*-* h8300-*-* } } } } */ Similarly, shouldn't attr-complex-method.c also search for __divsc3 for AVR, H8/300 and possibly a few other architectures?
next reply other threads:[~2024-03-01 0:34 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-01 0:34 jdx at o2 dot pl [this message] 2024-03-01 0:58 ` [Bug testsuite/114182] " pinskia at gcc dot gnu.org 2024-03-03 17:42 ` 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@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: linkBe 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).